SAMPLEThis is a sample for a sample company, “Mihon (Sample) Co., Ltd.”. It is not related to any real company or website.

KnownFor home
mihon.example.jp (10 public pages)
10/20/2026

mihon.example.jp — Website inspection report

Left as is, your company keeps missing prospects who come through AI, and harm using your site or name can happen.

Sales opportunity

In 7 of the 10 questions prospects ask AI, your company is not among the candidates.

Not named at the comparing, checking prices stage. First cause: "The home page never names the product"

Risk of harm

There is a serious security problem visible from outside, and 2 condition(s) match real incidents.

0 item(s) were fixed since the last inspection.

E

Overall rating (A–E)

Below GEO maturity Level 1 (Read). It stops at the security foundation.

A–E restates GEO maturity (below Level 1 = E, Level 1 = D, 2 = C, 3 = B, 4–5 = A).

Who reads what

ExecutivesCover, one-page summary, 01 incidents and 04 decisions (approval box). About five minutes to see what to decide.
IT and purchasing03 risk assessment and plan, and the appendix. The statement of work shows the scope and work time for budgets and contracts.
Web team and agency02 where you are, 05 fixing and after, and the statement of work: what to fix, where, how, and how to check, item by item.
Received on
Next inspection10/27/2026
Prepared byKnownFor AI guides

KnownFor AI guides are AI agents, not human staff. This inspection covers only what is visible from outside and does not guarantee safety.

One-page summary

10/20/2026

Overall

E / A–E

Alert level (security)

5 / 5

Questions where you were named

3 / 10

Cited in 0

Within your industry

2 of top 2

By how often AI names you

What is working

  • 12 of 19 security items have no problem
  • For questions like "工場のとき、どんなエアコンの節電用品がありますか", AI names your company

Biggest issues

  • Not named at the comparing, checking prices stage. First cause: "The home page never names the product"
  • There is a serious security problem visible from outside, and 2 condition(s) match real incidents.
SalesProspects who compare with AI do not see you as a candidate, and may choose another company first.
HarmThere is a serious security problem visible from outside, and 2 condition(s) match real incidents. (01)
TrustIf it happens, you may have to stop the site, explain and apologise (see the incidents in 01).

4 risk(s) above the act-now line (R1 Data leak, R2 Tampering, redirect to fake sites, R3 Impersonation, fraud, R4 Lost sales opportunity; heat map in 03)

To decideWho · work timeBy
1R1 Encrypt the form submissionWeb agency · half a day to 2 days10/27/2026
2R2, R3 Update old software and hide versions / Add the setting that stops spoofed emailWeb agency · 5–13 days11/19/2026
3R4 Write product names and comparison detailsIn-house · 3–11 days10/27/2026

Can be done this week without approval: A phone number different from the site’s own (1–2 hours in total)

Not covered by this inspection: legal compliance (copyright, advertising and other laws), pages behind login, penetration testing. Please consult a specialist if needed.

01

What actually happened on sites in the same condition

Mainly for: Executives

We matched what we found on your site with real incidents at other organisations (sourced ones only). It does not mean the same is happening to you or will happen.

Incident 1: Niigata University of Health and Welfare, Japan (2023)Same condition on your site

What happened

A weakness in the site’s content management system was used to rewrite pages so that visitors were automatically sent to a malicious site. The site was taken down for investigation.

On your site

The same condition was found.Software version numbers are visible from outside

How to stop itStop showing version numbers to the outside.

Source: ScanNetSecurity (Apr 7, 2023)

Incident 2: Request by Japan's MIC, National Police Agency and METI, Japan (2023)Same condition on your site

What happened

Japan's Ministry of Internal Affairs and Communications, the National Police Agency and the Ministry of Economy, Trade and Industry asked credit card companies to strengthen anti-phishing measures, as phishing emails posing as card companies were frequently leading users to fake sites to steal card numbers. Noting that phishing emails often spoof domain names, they asked companies to add DMARC to all public domains, including ones that send no email, and to run it with a policy that has receivers reject spoofed email.

On your site

The same condition was found.No DMARC policy for telling fake email apart

How to stop itAdd a DMARC record to DNS (start with monitoring only).

Source: Ministry of Internal Affairs and Communications (Feb 1, 2023)

Incident 3: Osaka City, Japan (2026)Similar condition on your site

What happened

On an event application form for a program the city outsourced, the contractor set the viewing settings incorrectly, so applicants could see what other applicants had entered. The names, school grades, phone and fax numbers, email addresses and reasons for applying of 40 people were affected. An applicant reported it on October 14, and the contractor fixed the setting the same day.

The cause was not encryption (https), but it is an example of form input being seen by others.

On your site

A similar condition exists.Forms that send data without protection

How to stop itMake the form send to an https address.

Source: Osaka City press release (Oct 15, 2026)

02

Where you are and what holds you back

Mainly for: Web team and agency

Overall

E / A–E

Alert level

5 / 5

Fixing the most urgent item lowers it to 3

Named by AI

3 / 10

Cited

0 / 10

Whether you were named, by stage of the question

StageQuestion (example)Named
Looking工場のとき、どんなエアコンの節電用品がありますか3/6
Comparingエアコンの節電用品の保守体制はどう比較すればよいですか0/2
Checking pricesエアコンの節電用品の納期と価格の目安を教えてください0/2

Found in AI answers (2)

  • AI does not cite the site
  • Field words missing on site
Biggest thing holding you back: The home page never names the productYou are not named at the comparing, checking prices stage. Visitors looking for your product leave because the home page does not say what you offer, and AI struggles to connect your company with it.

GEO maturity (how well AI guides people to you)

1 Read
2 Read correctly
3 Recommended
4 Cited
5 Driving action

You are below Level 1. While a basic security item has a serious problem, Level 1 cannot be reached however good the AI numbers are.

Compared with the last inspection

FixedStill thereNew or worse
0 21 2

We compare only with your own previous inspection.

03

Risk assessment and response plan

Mainly for: IT and purchasing

We grouped the 21 findings into 6 business risks and rated them by likelihood and impact. The further up and right, the bigger the risk; the red zone (15+ points) needs action now.

Impact (1 low → 5 high)
5
4
3
2
1
1
●1
23
▲2◆3
5
■5
★4
6
□6
1
2
3
4
5
Likelihood (1 low → 5 high)

Marker shape (risk type)

●Data leak
▲Tampering, redirect to fake sites
◆Impersonation, fraud
★Lost sales opportunity
■Wrong guidance
□Loss of trust
1Position after fixing

Tolerance (points = likelihood × impact)

15–25: act now
8–14: plan and act
1–7: accept and watch
RiskCause (what we found)PointsResponseWho · by · work timeAfter fixing
R1 ●Customers’ input is read (personal data leak)
Forms that send data without protection
5×5=25Reduce: Encrypt the form submissionWeb agency · 10/27 · half a day to 2 days1×5=5
R2 ▲Pages are rewritten and customers are led to fake sites
Software version numbers are visible from outside; An outdated JavaScript library; Protective headers are missing and 1 more
4×4=16Reduce: Update old software and hide versionsWeb agency · 11/19 · 5–11 days2×4=8
R3 ◆Fake emails in your company’s name harm partners
No DMARC policy for telling fake email apart
4×4=16Reduce: Add the setting that stops spoofed emailWeb agency · 11/19 · half a day to 2 days2×4=8
R4 ★Prospects coming through AI are lost
Not named by AI (7 of 10); The home page never names the product; Product pages have almost no explanation and 6 more
5×3=15Reduce: Write product names and comparison detailsIn-house · 10/27 · 3–11 daysMeasured with the same questions after 28 days
R5 ■AI gives the wrong contact number or page
A phone number different from the site’s own
3×3=9Reduce: Align phone numbers and guidance to one official sourceIn-house · 10/27 · 1–2 hours1×3=3
R6 □The site looks unfinished and loses trust
Template placeholder text is published; Menu labels do not match the page they open; The logo links somewhere other than home
3×2=6Accept and watch (fix when there is time)In-house · 11/19 · 6 hours to 3 days1×2=2

The 1–5 scales for likelihood and impact are at the end of this chapter. Positions after fixing follow fixed rules and are not forecasts.

Roadmap: who and by when Work time adds up the effort in the statement of work (small = 1–2 hours, medium = half a day to 2 days, large = 3–5 days). We do not show prices.

WhenMain itemsIn-houseWeb agencyKnownFor AI guide
This weekForms that send data without protection, The home page never names the product and 1 more2 · 2–4 hours1 · half a day to 2 days―
Within 30 daysProduct pages have almost no explanation, Template placeholder text is published and 10 more6 · 2–7 days6 · 6–15 days―
Within 60 daysThe main heading is only an image, Product pages lack Product structured data and 2 more1 · 1–2 hours2 · 5 hours to 3 days1 (drafts)
After the next inspectionBuying happens on another site, No llms.txt1 · 1–2 hours―1 (drafts)
Likelihood5: an exploited vulnerability is visible, or it is happening now4: the same condition as a real incident3: machines can find it from outside, or AI answers actually got it wrong2: happens only combined with other gaps1: theoretical
Impact5: personal data leak, financial loss4: tampering, outage, harm to partners3: wrong guidance, or many prospects lost2: loss of trust1: minor
04

Decisions we need from you

Mainly for: Executives

Tick your choice and write who decided and when. You can also record it on screen; the next report checks it.

1R1 Encrypt the form submissionrisk of harmBy 10/27/2026

If not decided

R1 (25 points) remain: Customers’ input is read (personal data leak)

If fixed

Scores drop: R1 25→5

Who · work time

Web agency · 1 item(s) · half a day to 2 days
FixPostpone with a date (reason: ______)Consult a specialist
Decided by
Date
Requested on
2R2, R3 Update old software and hide versions / Add the setting that stops spoofed emailrisk of harmBy 11/19/2026

If not decided

R2 (16 points), R3 (16 points) remain: Pages are rewritten and customers are led to fake sites / Fake emails in your company’s name harm partners

If fixed

Scores drop: R2 16→8, R3 16→8

Who · work time

Web agency · 5 item(s) · 5–13 days
FixPostpone with a date (reason: ______)Consult a specialist
Decided by
Date
Requested on
3R4 Write product names and comparison detailssales opportunityBy 10/27/2026

If not decided

R4 (15 points) remain: Prospects coming through AI are lost

If fixed

It gives AI grounds to guide people to you. We measure with the same questions 28 days after the fix.

Who · work time

In-house · 6 item(s) · 3–11 days
Assign and go aheadPostpone with a date (reason: ______)Consult a specialist
Decided by · owner
Date
Done by
After you know: No new duty is added. Companies handling personal data already have security duties under Japan’s personal information law (Article 23). Keeping the date received and what you decided lets you explain what you did after you knew (not legal advice).
05

When fixing, and after

Mainly for: Web team and agency

Statement of work (separate)

Each item has how to fix it, when it counts as done and how to check it. The scope a web agency needs for a quote is in it too.

After fixing

To check the fix by the same rules, use another one-time inspection or a continuing plan. A continuing plan inspects automatically every week, and the next inspection report checks what you decided in 04 and shows how the risk scores moved.

Some fixes tend to slip back during routine work

Many findings sit where routine work (server updates, contractor changes, new pages) brings them back. Setting a rule to check at those moments prevents the next problem as much as fixing does.

Work where fixes slip backWhose workWhen it slips backNow
Server configuration changesYour web teamWhen settings change4
Publishing and redesign stepsYour web teamWhen settings change4
Rules for new pagesYour teamNew pages, new staff11
Updating contact details everywhereYour teamNew pages, new staff1
Expiry dates (certificates, domains)Your web teamWhen a date comesdue 12/1/2026
Software updatesYour web teamWhen a date comes2
Email sending settingsYour web teamWhen settings change1

For example: Hand over a checklist whenever the server or vendor changes / Run one re-scan after each change

AAppendix · Pages

Of the 10 public pages read, the 10 pages with findings are listed (numbers on the right match the statements of work).

PageClicks from homeStatement
見本株式会社 | 総合的なビジネスパートナー
Home page
0P-02 P-16
サービス内容 | 見本株式会社
/services
1P-08 P-12 P-16
商材 | 見本株式会社
/products
1P-06 P-08 P-16
お客様の声 | 見本株式会社
/voice
1P-05 P-08 P-16
採用情報 | 見本株式会社
/recruit
1P-16
会社概要 | 見本株式会社
/company
1P-16
Fold-M210S | 見本株式会社
/products/fold-m210s
2P-04 P-08 P-16 P-17 P-20
クリアミナモ | 見本株式会社
/products/クリアミナモ
2P-04 P-08 P-16
thank | 見本株式会社
/thank
unreachableP-03 P-16 P-18
お問い合わせ | 見本株式会社
/contact
unreachableP-07 P-16
BAppendix · Questions asked to AI

クリアミナモ

QQuestionNamedCited
1“工場のとき、どんなエアコンの節電用品がありますか” (original text)✓×
2“事務所の工程で電気代の削減を改善するには、どんな設備が使われますか” (original text)××
3“エアコンの節電用品を選ぶとき、納期で比べるとどのメーカーが候補になりますか” (original text)✓×
4“エアコンの節電用品の納期と価格の目安を教えてください” (original text)××
5“エアコンの節電用品の保守体制はどう比較すればよいですか” (original text)××

Fold-M210S

QQuestionNamedCited
1“工場のとき、どんなエアコンの節電用品がありますか” (original text)✓×
2“事務所の工程で電気代の削減を改善するには、どんな設備が使われますか” (original text)××
3“エアコンの節電用品を選ぶとき、納期で比べるとどのメーカーが候補になりますか” (original text)××
4“エアコンの節電用品の納期と価格の目安を教えてください” (original text)××
5“エアコンの節電用品の保守体制はどう比較すればよいですか” (original text)××

Full answers are shown in KnownFor (ask your contact).

CAppendix · Configuration examples

General examples. Please confirm with your web team that an example suits your site before applying it. They are the same as Appendix C of the statement of work.

Apache (.htaccess): protective headersP-13
# .htaccess (Apache) - add after the https redirect
<IfModule mod_headers.c>
  Header always set Strict-Transport-Security "max-age=31536000"
  Header always set Content-Security-Policy "frame-ancestors 'self'"
  Header always set X-Content-Type-Options "nosniff"
</IfModule>
WordPress (child theme functions.php): protective headersP-13
// WordPress (child theme functions.php)
add_action('send_headers', function () {
  header('Strict-Transport-Security: max-age=31536000');
  header("Content-Security-Policy: frame-ancestors 'self'");
  header('X-Content-Type-Options: nosniff');
});
Apache: hide the versionP-10
# httpd.conf / apache2.conf
ServerTokens Prod
ServerSignature Off
PHP: hide the versionP-10
; php.ini
expose_php = Off
WordPress: hide the generator versionP-10
// WordPress (child theme functions.php)
remove_action('wp_head', 'wp_generator');
add_filter('the_generator', '__return_empty_string');
DNS: DMARC (monitor first)P-14
; DNS TXT record - review the reports first, then tighten step by step
_dmarc.example.jp.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.jp"
DAppendix · How we checked, and what we did not

Today, AI reads the pages and writes an answer before people open them, and cyber attackers look at the same pages from outside by machine. This report inspects, on one line called GEO maturity, how far the site has grown inside AI answers, with the security visible from outside as its base.

TargetPublic pages of mihon.example.jp. We read 10 pages, starting with the most important. The whole site may be larger. Pages behind a login were not read.
AI answersWe asked AI (Gemini) the questions buyers are likely to ask, per product (without your name; 10 in total). We checked whether you were named and whether your site was cited.
How we askedWe asked Gemini (gemini-3.6-flash) with web search on, once per question, around 12:00 on 10/20/2026. AI answers can change each time, so this is one snapshot. The next inspection asks the same questions to the same AI and compares.
SecurityWe checked 19 items anyone can see from outside (encryption, certificate expiry, browser security settings, software versions shown, email sender checks, etc.). Judgments follow fixed rules without AI, so anyone gets the same result.
GEO maturityThe criteria (GEO Maturity Model) are published at www.knownfor.jp/en/maturity/. An inspection can see security, search and AI reading settings, and the numbers in AI answers. AI crawler visits (Cloudflare), Google’s index (Search Console) and visits and inquiries from AI (GA4) cannot be seen in an inspection, so they are marked “no record”.

Items with no issues found (12). None of the following were found: No redirect from http to https / An https page loads http content / Cookies without protection flags / DMARC is set to monitor only / No SPF record to check where email comes from / The SPF record does not restrict senders / The certificate expires soon (or has expired) / Server software (such as PHP) shows a version with publicly known vulnerabilities / Runs on PHP, and the vulnerability fix cannot be confirmed from outside / A version affected by a known exploited vulnerability is visible / Scripts loaded from outside lack tamper protection (SRI) / Signs of tampering (clusters of unrelated spam words) are visible

What we did not check

  • Inside the server, admin screens, member areas and other places not visible from outside
  • Cipher strength, and weaknesses of each plugin (only versions visible from outside were checked)
  • Other subdomains, external links, and pages blocked by robots.txt
  • Answers from AI other than the one we asked, and whether everything in the answers is correct
  • This does not replace a penetration test or security assessment. If you need a deeper check, we can introduce specialist firms.

How to read

SeriousHarm can happen if left (only what machines confirmed)
WarningNot harmful now, but a foothold for attacks or misdirection
MinorWorth tidying; not urgent. “No record” in GEO maturity is also shown in gray
No issuesNothing found within what was checked
“Nothing found” does not mean “safe” or “no problem”; it means nothing was found within the items checked. AI answers change from day to day even if the site does not. We compare numbers with the same questions, AI and period.
EAppendix · Terms and sources
GEO maturityA five-level scale (Read, Read correctly, Recommended, Cited, Driving action) showing, on one line from externally visible security to people’s actions, how far a website has grown inside generative AI answers.
Alert levelThe danger level of the security visible from outside (5 steps). 5 is the most dangerous, like Japan’s disaster alert levels — the opposite direction from GEO maturity levels.
Verification windowThe period (28 days) we wait after a fix, without counting, before saying whether it worked.
No recordNo material, so neither passed nor not yet. Never filled in by guesswork.
CitedWhen an AI answer uses the site as its source (link).
HSTSA setting telling browsers to always open the site over https.
SPF / DMARCSettings that let receivers check whether an email’s sender is genuine. DMARC has stages: monitor, quarantine, reject.
Description (meta description)A one- or two-sentence description search and AI use to introduce a page.
llms.txtA text file that tells AI what the site is and its key pages (optional).
Statement of workA separate document for your web team with steps, completion criteria and what to report for each finding.
Niigata University of Health and Welfare, Japan (2023)
ScanNetSecurity (Apr 7, 2023) https://scan.netsecurity.ne.jp/article/2023/04/07/49179.html
Figures on cyber attackers
National Police Agency, cyber threat report for H1 2026 (Sep 2026), p.5
NICT, NICTER Observation Report 2025 (Feb 2026) / National Police Agency 2025 report, p.19
National Police Agency, H1 2026, pp.9–10
IPA, 10 Major Security Threats 2026 [Organizations]
This report covers what is visible from outside. “Nothing found” does not mean “safe”. By KnownFor (株式会社アーグマックス) · www.knownfor.jp
Restricted
A list of work you can hand to your web team as is 10/20/2026

mihon.example.jp
Statement of work

Page structure · Read by AI and search

14 items

Let AI and search read it correctly: work on descriptions, headings, guidance for AI, etc.

P-02P-03P-04P-05P-06P-07+8 more

Security · Gaps visible from outside

7 items

Close the gaps visible from outside: work on server, email and browser security settings.

P-01P-10P-11P-13P-14P-15+1 more

First work items (6 of 21)

P-01Forms that send data without protectionSeriousWeb teamThis week
P-02The home page never names the productSeriousYouThis week
P-03A phone number different from the site’s ownSeriousYouThis week
P-04Product pages have almost no explanationSeriousYouWithin 30 days
P-05Template placeholder text is publishedWarningYouWithin 30 days
P-06Menu labels do not match the page they openWarningYouWithin 30 days

The full list of 21 items is on the next page.

Target
mihon.example.jp
Inspected
10/20/2026 · Made 10/20/2026
By
KnownFor (株式会社アーグマックス)
Use only for this work. Numbers match the report.
SOWSTATEMENT OF WORK

Each item can be used as a request as is.

All work items (21)

No.What to doSeverityWhoWhen
P-01Forms that send data without protectionSeriousWeb teamThis week
P-02The home page never names the productSeriousYouThis week
P-03A phone number different from the site’s ownSeriousYouThis week
P-04Product pages have almost no explanationSeriousYouWithin 30 days
P-05Template placeholder text is publishedWarningYouWithin 30 days
P-06Menu labels do not match the page they openWarningYouWithin 30 days
P-07Pages not linked from home but open to search and AIWarningYouWithin 30 days
P-08Pages without a meta descriptionWarningYouWithin 30 days
P-09The member site’s value is not explained on public pagesWarningYouWithin 30 days
P-10Software version numbers are visible from outsideWarningWeb teamWithin 30 days
P-11An outdated JavaScript libraryWarningWeb teamWithin 30 days
P-12The logo links somewhere other than homeWarningWeb teamWithin 30 days
P-13Protective headers are missingWarningWeb teamWithin 30 days
P-14No DMARC policy for telling fake email apartWarningWeb teamWithin 30 days
P-15Software that is no longer supported is visibleWarningWeb teamWithin 30 days
P-16The main heading is only an imageWarningWeb teamWithin 60 days
P-17Product pages lack Product structured dataWarningKnownForWithin 60 days
P-18A form completion page is in the sitemapMinorYouWithin 60 days
P-19No security contact (security.txt) is publishedMinorWeb teamWithin 60 days
P-20Buying happens on another siteMinorYouAfter the next inspection
P-21No llms.txtMinorKnownForAfter the next inspection

Conditions common to all work

Out of scope (what not to do)
  • Only the changes needed to fix this item are included. Other changes to design or structure, and new features, are not. Quote them separately if needed.
Please report
  • Date of work and who did it
  • What was changed (files, settings, pages), before and after
  • How each completion condition was checked, with screenshots
  • The rollback procedure
  • A hand-over record (so this change is not lost in future redesigns, server moves or contractor changes)
Estimate
  • Before starting, send an estimate of effort, cost and work date, and state whether it is covered by the maintenance contract.

Items the client judges to be intended can be recorded on the KnownFor screen; they no longer appear from the next inspection and are out of scope.

The numbers follow the order of work and match the report (P-01, etc.).

P-01SeriousSecurityEffort MediumThis weekForms that send data without protection
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-01)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Forms that send data without protection
  1. What this item means
    • The address that form input is sent to is an unencrypted http address.
  2. Purpose (why fix it)
    • What visitors type is sent without encryption.
  1. Current state (what was found)
    • 1 form(s) send to an http:// address, or a password field is on an http page (1 page(s)). What is typed is sent unencrypted.
    • Target: the whole site (server settings) (found at e.g. https://mihon.example.jp/contact)
  2. Scope of work (what to do)
    • Please change form targets (action) to https:// and make pages with password fields open over https.
  3. Completion criteria (done when all are met)
    • The change takes effect across the whole site (every page, not just some).
    • After the change, every page still displays and works as before.
    • At KnownFor’s next scan, this item (P-01) no longer appears.
  4. Cautions
    • Record the current settings before starting (so you can roll back).
    • Check that embedded external components (maps, video, analytics) keep working.
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-02SeriousSiteEffort SmallThis weekThe home page never names the product
How to check
After the fix, open the home page and check that the product names show as text; the next scan checks it automatically too.
How to fix: Statement of work(P-02)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] The home page never names the product
  1. Purpose (why fix it)
    • Visitors looking for your product leave because the home page does not say what you offer, and AI struggles to connect your company with it.
  2. Current state (what was found)
    • The home page never mentions “Fold-M210S”, “クリアミナモ”, and neither does its meta description.
    • Target pages: 1 (e.g. https://mihon.example.jp/)
  1. Scope of work (what to do)
    • Please put the product names as text in an easy-to-see place on the home (top) page and link each to its product page. Please do not use images only.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-02) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
In the editor for the home page, add a “Main products” heading where it is easy to see, write the product names as text and link each one to its page.
WordPress: WordPress admin → Pages → open “Home” → “+” → “Heading” → type the product name → select the text, use the chain button to link to the product page → “Update”. (Screens differ by theme.)
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-03SeriousSiteEffort SmallThis weekA phone number different from the site’s own
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-03)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] A phone number different from the site’s own
  1. Purpose (why fix it)
    • Calls may go to the wrong number, and inquiries can be lost.
  2. Current state (what was found)
    • “/thank” shows a phone number different from the site’s own (0600002222).
    • Target pages: 1 (e.g. https://mihon.example.jp/thank)
  1. Scope of work (what to do)
    • Please label numbers that differ from the main number (store, FAX, etc.) or switch them to the main number.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-03) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
Add a label such as “store” or “FAX” next to the number, or use the main number.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-04SeriousSiteEffort MediumWithin 30 daysProduct pages have almost no explanation
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-04)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Product pages have almost no explanation
  1. Purpose (why fix it)
    • Without the answers buyers need, inquiries drop — and AI answers using other sites’ descriptions instead of yours.
  2. Current state (what was found)
    • Product pages have almost no text explaining what the product is for and how to use it (Fold-M210S: 67 characters, クリアミナモ: 23 characters).
    • Target pages: 2 (e.g. https://mihon.example.jp/products/fold-m210s, https://mihon.example.jp/products/クリアミナモ)
  1. Scope of work (what to do)
    • Please add at least 400 characters explaining uses, target users, features, specs and usage to each product page, as text rather than inside images.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-04) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
On each product page add headings such as “Uses”, “Who it is for”, “Features”, “Specs” and “How to use”, and write each as text (not inside images).
WordPress: Pages (or Posts) → open the product page → add headings and write text → “Update”.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-05WarningSiteEffort SmallWithin 30 daysTemplate placeholder text is published
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-05)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Template placeholder text is published
  1. Purpose (why fix it)
    • The site looks unfinished, which lowers trust in the company.
  2. Current state (what was found)
    • Template placeholder text (テキストテキスト…, ○○○) remains on 1 page(s).
    • Target pages: 1 (e.g. https://mihon.example.jp/voice)
  1. Scope of work (what to do)
    • Please replace the template text on these pages with real text, or unpublish them.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-05) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
Replace the template text with real text. Unpublish pages you do not use.
WordPress: Pages → the page → replace the template text with real text. Switch unused pages back to “Draft”.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-06WarningSiteEffort SmallWithin 30 daysMenu labels do not match the page they open
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-06)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Menu labels do not match the page they open
  1. Purpose (why fix it)
    • Visitors and AI find that the destination differs from what they expected.
  2. Current state (what was found)
    • Menu labels differ from the page they open: “プロダクト事業” → “商材”.
    • Target pages: 1 (e.g. https://mihon.example.jp/products)
  1. Scope of work (what to do)
    • Please make the menu labels match the names of the pages they open.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-06) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
Make each menu item’s name match the name of the page it opens.
WordPress: Appearance → Menus → open the item → set “Navigation Label” to the page name → save.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-07WarningSiteEffort SmallWithin 30 daysPages not linked from home but open to search and AI
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-07)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Pages not linked from home but open to search and AI
  1. Purpose (why fix it)
    • Pages you did not mean to show can be opened directly from search and AI.
  2. Current state (what was found)
    • 1 page(s) cannot be reached from the home page, but they are in the sitemap, so search engines and AI can open them directly.
    • Target pages: 1 (e.g. https://mihon.example.jp/contact)
  1. Scope of work (what to do)
    • Please link pages that home cannot reach from the menu or text, or unpublish the ones that should stay hidden.
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-07) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
If you want the page seen, link to it from home or the menu. If not, unpublish it.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-08WarningSiteEffort MediumWithin 30 daysPages without a meta description
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-08)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Pages without a meta description
  1. What this item means
    • Web pages have a field, separate from the body, for one or two sentences saying what the page is (meta description). It is not shown on screen; it is an introduction read by search engines and AI. Without it, they summarize the body automatically and may pick up unimportant parts.
  2. Purpose (why fix it)
    • Search engines and AI describe your pages in auto-generated words.
  1. Current state (what was found)
    • 5 page(s) reachable from the home page have no meta description.
    • Target pages: 5 (e.g. https://mihon.example.jp/services, https://mihon.example.jp/products, https://mihon.example.jp/voice, and more)
  2. Scope of work (what to do)
    • Please add a one or two sentence meta description to pages that lack one.
    • Start with your main products and services and the contact page. You do not need to fix every page at once.
  3. Completion criteria (done when all are met)
    • It is fixed on the pages agreed as the priority in the scope above, and the remaining pages are scheduled.
    • At KnownFor’s next scan, this item (P-08) no longer appears on the priority pages.
  4. Cautions
    • Get approval from our staff contact before changing text or images.
  5. Notes (what to expect and not expect)
    • This is not a security hole. It does not by itself make AI answers correct; it is one aid to improvement.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
In each page’s settings, write the page description (meta description) in one or two sentences.
WordPress: Edit the page → the SEO plugin box below (e.g. AIOSEO) → write one or two sentences in “Meta description” → “Update”. (Names differ by version.)
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-09WarningSiteEffort MediumWithin 30 daysThe member site’s value is not explained on public pages
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-09)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] The member site’s value is not explained on public pages
  1. Purpose (why fix it)
    • AI cannot explain why to become a member, so your member site’s strengths go unmentioned.
  2. Current state (what was found)
    • AI cannot read inside the member site (1 entrance(s)). No public page explains what members can do, so AI cannot describe the member site’s value.
    • Target pages: 1 (e.g. https://mihon.example.jp/mypage)
  1. Scope of work (what to do)
    • Please add a public page explaining why to become a member (features, information members get).
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-09) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
On a public page, write what members can use (the member area itself is not read).
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-10WarningSecurityEffort MediumWithin 30 daysSoftware version numbers are visible from outside
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-10)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Software version numbers are visible from outside
  1. What this item means
    • The server or software shows its version number to the outside. Attackers use these numbers to check whether a version has weaknesses.
  2. Purpose (why fix it)
    • Visible version numbers are a clue for finding publicly known weaknesses of that version (finding is not the same as harm).
  1. Current state (what was found)
    • This information is visible to anyone from outside: Apache 2.4.41, PHP 7.4.3, WordPress 6.4.2, plugin all-in-one-seo-pack 4.5.0.
    • Values seen from outside: Server: Apache/2.4.41 (Ubuntu) / X-Powered-By: PHP/7.4.3 / generator: WordPress 6.4.2 / plugin: all-in-one-seo-pack 4.5.0
    • Target pages: 10 (e.g. https://mihon.example.jp/, https://mihon.example.jp/services, https://mihon.example.jp/products, and more)
  2. Scope of work (what to do)
    • Please configure the site to hide software version numbers (Server, X-Powered-By, generator, ?ver=) from page output and response headers. Examples are in Appendix C.
    • Configuration examples matching the server type are in Appendix C of this statement of work.
  3. Completion criteria (done when all are met)
    • The software and components on the site are on versions still supported by their makers.
    • Version numbers cannot be read from outside via response headers, HTML or file names.
    • After the update, every page still displays and works as before (forms, search, menus).
    • At KnownFor’s next scan, this item (P-10) no longer appears.
  4. Cautions
    • Take a full backup of the site before starting.
    • Check display and functions in a test environment before production.
    • Prepare a rollback procedure before you start.
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
Check updates in the admin screen and update anything out of date (back up first). Ask your web team to hide the version display.
WordPress: Admin → Dashboard → Updates: update anything out of date (back up first).
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-11WarningSecurityEffort MediumWithin 30 daysAn outdated JavaScript library
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-11)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] An outdated JavaScript library
  1. What this item means
    • An old version of a component that makes pages work (a JavaScript library) is in use.
  2. Purpose (why fix it)
    • Publicly known weaknesses remain unfixed in this version. Depending on how the site uses it (whether input from outside is put on the page through this library), it can be exploited. How it is used cannot be seen from outside.
  1. Current state (what was found)
    • Based on what is shown (file names): jQuery 3.3.1 has publicly known weaknesses (CVE-2020-11022, CVE-2020-11023), fixed in 3.5.0 and later. What is shown may differ from what actually runs (for example, when a distributor has applied fixes).
    • Values seen from outside: /wp-includes/js/jquery/jquery-3.3.1.min.js
    • Target pages: 10 (e.g. https://mihon.example.jp/, https://mihon.example.jp/services, https://mihon.example.jp/products, and more)
  2. Scope of work (what to do)
    • Please update the outdated JavaScript library the site loads to the latest stable version, and check display and behavior afterwards.
  3. Completion criteria (done when all are met)
    • The software and components on the site are on versions still supported by their makers.
    • Version numbers cannot be read from outside via response headers, HTML or file names.
    • After the update, every page still displays and works as before (forms, search, menus).
    • At KnownFor’s next scan, this item (P-11) no longer appears.
  4. Cautions
    • Take a full backup of the site before starting.
    • Check display and functions in a test environment before production.
    • Prepare a rollback procedure before you start.
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-12WarningSiteEffort MediumWithin 30 daysThe logo links somewhere other than home
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-12)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] The logo links somewhere other than home
  1. Purpose (why fix it)
    • A logo is read as “back to home”, so it can look like a different entrance.
  2. Current state (what was found)
    • Clicking the logo goes to “サービス内容” instead of the home page (a logo usually returns home).
    • Target pages: 1 (e.g. https://mihon.example.jp/services)
  1. Scope of work (what to do)
    • Please change the logo link to the home page (/).
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-12) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-13WarningSecurityEffort MediumWithin 30 daysProtective headers are missing
How to check
After the fix, check that the headers are returned. The next scan checks it too.
How to fix: Statement of work(P-13)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Protective headers are missing
  1. What this item means
    • Settings in which the server tells browsers how to protect the site (response headers) are missing. They prevent things such as being embedded in other sites or being downgraded to unencrypted connections.
  2. Purpose (why fix it)
    • The browser’s protective features are not switched on (finding this is not the same as harm).
  1. Current state (what was found)
    • The home page response lacks these protective headers: HSTS (Strict-Transport-Security), CSP (Content-Security-Policy) or X-Frame-Options, X-Content-Type-Options.
    • Target: the whole site (server settings) (found at e.g. https://mihon.example.jp/)
  2. Scope of work (what to do)
    • Please add the Strict-Transport-Security, Content-Security-Policy (frame-ancestors), X-Content-Type-Options headers to the server response. Examples are in Appendix C. Set up the https redirect first.
    • Configuration examples matching the server type are in Appendix C of this statement of work.
  3. Completion criteria (done when all are met)
    • The change takes effect across the whole site (every page, not just some).
    • After the change, every page still displays and works as before.
    • At KnownFor’s next scan, this item (P-13) no longer appears.
  4. Cautions
    • Record the current settings before starting (so you can roll back).
    • Check that embedded external components (maps, video, analytics) keep working.
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-14WarningSecurityEffort MediumWithin 30 daysNo DMARC policy for telling fake email apart
How to check
After the fix, check the DNS record. The next scan checks it too.
How to fix: Statement of work(P-14)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] No DMARC policy for telling fake email apart
  1. What this item means
    • DMARC is a DNS setting that tells receiving servers what to do with email claiming to be from this domain that fails the checks. It is missing.
  2. Purpose (why fix it)
    • Receiving mail servers have a harder time telling fake email that uses the company’s name.
  1. Current state (what was found)
    • There is no DMARC policy, the setting that lets receiving mail servers tell fake email using the company's name apart (example.jp).
    • Target: the whole domain (DNS settings)
  2. Scope of work (what to do)
    • Please add a DMARC record (TXT at _dmarc) to the domain’s DNS. Start with p=none (monitor only), review the reports, then tighten step by step. An example is in Appendix C.
    • Configuration examples matching the server type are in Appendix C of this statement of work.
  3. Completion criteria (done when all are met)
    • The new records (SPF, DMARC) can be looked up in public DNS.
    • All email sent in our name (including contractors and delivery services) still arrives after the change.
    • At KnownFor’s next scan, this item (P-14) no longer appears.
  4. Cautions
    • First list every sender (our own mail, contractors, delivery services). Missing one will stop its mail from arriving.
    • Tighten DMARC one step at a time after reviewing the reports (when adding it for the first time, start with monitoring only).
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-15WarningSecurityEffort LargeWithin 30 daysSoftware that is no longer supported is visible
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-15)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Software that is no longer supported is visible
  1. What this item means
    • Some software or components on the site are on versions for which the maker no longer releases fixes. Weaknesses in unsupported versions are not fixed even when found.
  2. Purpose (why fix it)
    • Versions that are no longer supported get no fixes from their makers for weaknesses found later. Depending on how the site uses them and how it is set up, they can be exploited. How they are used and set up cannot be seen from outside.
  1. Current state (what was found)
    • Based on what is shown (file names, headers), these versions are no longer supported (their makers no longer release fixes; EOL): PHP 7.4.3. PHP 7.4 reached end of support on 2022-11-28. What is shown may differ from what actually runs (for example, when a distributor has applied fixes).
    • Values seen from outside: X-Powered-By: PHP/7.4.3
    • Target pages: 10 (e.g. https://mihon.example.jp/, https://mihon.example.jp/services, https://mihon.example.jp/products, and more)
  2. Scope of work (what to do)
    • Please update software that is no longer supported to a supported version. Back up first and check display and behavior afterwards.
  3. Completion criteria (done when all are met)
    • The software and components on the site are on versions still supported by their makers.
    • Version numbers cannot be read from outside via response headers, HTML or file names.
    • After the update, every page still displays and works as before (forms, search, menus).
    • At KnownFor’s next scan, this item (P-15) no longer appears.
  4. Cautions
    • Take a full backup of the site before starting.
    • Check display and functions in a test environment before production.
    • Prepare a rollback procedure before you start.
  5. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  6. Requested deadline
    • By 10/27/2026 (before the next scan)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-16WarningSiteEffort MediumWithin 60 daysThe main heading is only an image
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-16)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] The main heading is only an image
  1. What this item means
    • The page’s main heading (h1) is only an image (such as a logo), not text. Text inside images is hard for search engines, AI and screen readers to understand as what the page is about.
  2. Purpose (why fix it)
    • Machines have a harder time telling what each page is about.
  1. Current state (what was found)
    • On 10 page(s), the main heading (h1) is only an image (the logo).
    • Target pages: 10 (e.g. https://mihon.example.jp/, https://mihon.example.jp/services, https://mihon.example.jp/products, and more)
  2. Scope of work (what to do)
    • Please make each page’s main heading (h1) text, not an image.
    • Start with your main products and services and the contact page. You do not need to fix every page at once.
  3. Completion criteria (done when all are met)
    • It is fixed on the pages agreed as the priority in the scope above, and the remaining pages are scheduled.
    • At KnownFor’s next scan, this item (P-16) no longer appears on the priority pages.
  4. Cautions
    • Get approval from our staff contact before changing text or images.
  5. Requested deadline
    • By 12/19/2026 (within 60 days)
If you fix it yourself
You may be able to fix this in the site admin screen. If not, give the work instructions above to your web team.
WordPress: Edit the page → put the heading in a Heading block as text (the image heading may stay).
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-17WarningSiteEffort MediumWithin 60 daysProduct pages lack Product structured data
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-17)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Product pages lack Product structured data
  1. What this item means
    • There is no structured data that adds page content (names, prices, etc.) in a machine-readable form.
  2. Purpose (why fix it)
    • AI may not read your prices and specs correctly.
  1. Current state (what was found)
    • 1 product page(s) have no Product structured data.
    • Target pages: 1 (e.g. https://mihon.example.jp/products/fold-m210s)
  2. Scope of work (what to do)
    • Please add Product structured data (JSON-LD: name, description, image, price or specs) to the product pages.
  3. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-17) no longer appears.
  4. Cautions
    • Get approval from our staff contact before changing text or images.
  5. Requested deadline
    • By 12/19/2026 (within 60 days)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-18MinorSiteEffort SmallWithin 60 daysA form completion page is in the sitemap
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-18)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] A form completion page is in the sitemap
  1. Purpose (why fix it)
    • Search and AI can open the page shown after a form is sent directly.
  2. Current state (what was found)
    • A page shown after a form is sent (/thank) is in the sitemap. Keep the page and take it out of the sitemap.
    • Target pages: 1 (e.g. https://mihon.example.jp/thank)
  1. Scope of work (what to do)
    • Please take the completion page out of the sitemap and add noindex. Keep the page itself.
  2. Completion criteria (done when all are met)
    • Search and AI access works as intended (robots.txt, noindex, sitemap).
    • At KnownFor’s next scan, this item (P-18) no longer appears.
  3. Cautions
    • Before the change, check the list so pages you do not want in search do not appear.
  4. Notes (what to expect and not expect)
    • This alone does not guarantee that AI answers will change.
  5. Requested deadline
    • By 12/19/2026 (within 60 days)
If you fix it yourself
In the SEO plugin or sitemap settings, take the completion page out of the sitemap. Do not delete the page (the screen after the form would disappear).
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-19MinorSecurityEffort SmallWithin 60 daysNo security contact (security.txt) is published
How to check
After the fix, open /.well-known/security.txt in a browser to check. The next scan checks it too.
How to fix: Statement of work(P-19)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] No security contact (security.txt) is published
  1. Purpose (why fix it)
    • People who notice a weakness do not know where to report it (this is not a weakness itself).
  2. Current state (what was found)
    • There is no published guide (/.well-known/security.txt) for people who find a weakness to report it.
    • Target: the whole site (server settings) (found at e.g. https://mihon.example.jp/)
  1. Scope of work (what to do)
    • Please place a text file at /.well-known/security.txt with a contact (Contact:) and an expiry (Expires:) (RFC 9116). Use the responsible team’s email address or a contact page.
  2. Completion criteria (done when all are met)
    • The change takes effect across the whole site (every page, not just some).
    • After the change, every page still displays and works as before.
    • At KnownFor’s next scan, this item (P-19) no longer appears.
  3. Cautions
    • Record the current settings before starting (so you can roll back).
    • Check that embedded external components (maps, video, analytics) keep working.
  4. Notes (what to expect and not expect)
    • This check covers only what is visible from outside. Finding it is not the same as harm having occurred.
  5. Requested deadline
    • By 12/19/2026 (within 60 days)
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-20MinorSiteEffort SmallAfter the next inspectionBuying happens on another site
How to check
We check it automatically at the next scan.
How to fix: Statement of work(P-20)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] Buying happens on another site
  1. Purpose (why fix it)
    • This is often not a problem. With a purchase note on the product page, AI can explain how to buy.
  2. Current state (what was found)
    • Buying “Fold-M210S” sends visitors to another site (shop-sample.example). Check that companies buying in bulk have a way in.
    • Target pages: 1 (e.g. https://mihon.example.jp/products/fold-m210s)
  1. Scope of work (what to do)
    • Please add a sentence on the product page saying where it can be bought (optional).
  2. Completion criteria (done when all are met)
    • It is fixed on every target page (not just some of them).
    • At KnownFor’s next scan, this item (P-20) no longer appears.
  3. Cautions
    • Get approval from our staff contact before changing text or images.
  4. Requested deadline
    • No rush. Review after the next inspection
If you fix it yourself
Write on the product page, in text, where it can be bought (optional).
☐ Started☐ Fixed☐ Re-checkedOwnerDue
P-21MinorSiteEffort SmallAfter the next inspectionNo llms.txt
How to check
The next scan checks /llms.txt automatically.
How to fix: Statement of work(P-21)Hand this to your web team as is. It sets the completion criteria up front.
[mihon.example.jp] No llms.txt
  1. What this item means
    • llms.txt is a text file that gives AI an overview of the site and a list of its main pages (optional).
  2. Purpose (why fix it)
    • Even if you add one, AI may not read it. It does no harm, but large studies have not yet confirmed that it changes AI’s answers. It is optional.
  1. Current state (what was found)
    • There is no llms.txt.
  2. Scope of work (what to do)
    • Please place a text file at /llms.txt describing the site and listing the main pages.
  3. Completion criteria (done when all are met)
    • Search and AI access works as intended (robots.txt, noindex, sitemap).
    • At KnownFor’s next scan, this item (P-21) no longer appears.
  4. Cautions
    • Before the change, check the list so pages you do not want in search do not appear.
  5. Notes (what to expect and not expect)
    • AI may not read it even if added. It is optional.
  6. Requested deadline
    • No rush. Review after the next inspection
If you fix it yourself
There is nothing to fix directly yourself. Give the statement of work above to your web team.
☐ Started☐ Fixed☐ Re-checkedOwnerDue

App. APages with problems

Of the 10 pages in the list, all 10 pages with problems are listed. The P numbers on the right match this statement of work.

PageClicks from homeInbound linksProblems found
見本株式会社 | 総合的なビジネスパートナー
/
09Serious P-02Warning P-16
サービス内容 | 見本株式会社
/services
19Warning P-08Warning P-12Warning P-16
商材 | 見本株式会社
/products
19Warning P-06Warning P-08Warning P-16
お客様の声 | 見本株式会社
/voice
19Warning P-05Warning P-08Warning P-16
採用情報 | 見本株式会社
/recruit
19Warning P-16
会社概要 | 見本株式会社
/company
11Warning P-16
Fold-M210S | 見本株式会社
/products/fold-m210s
21Serious P-04Warning P-08Warning P-16Warning P-17Minor P-20
クリアミナモ | 見本株式会社
/products/クリアミナモ
21Serious P-04Warning P-08Warning P-16
thank | 見本株式会社
/thank
unreachable0Serious P-03Warning P-16Minor P-18
お問い合わせ | 見本株式会社
/contact
unreachable0Warning P-07Warning P-16

App. CConfiguration examples

Please confirm with your web team that an example suits your site before applying it.

Apache (.htaccess): protective headersP-13
# .htaccess (Apache) - add after the https redirect
<IfModule mod_headers.c>
  Header always set Strict-Transport-Security "max-age=31536000"
  Header always set Content-Security-Policy "frame-ancestors 'self'"
  Header always set X-Content-Type-Options "nosniff"
</IfModule>
WordPress (child theme functions.php): protective headersP-13
// WordPress (child theme functions.php)
add_action('send_headers', function () {
  header('Strict-Transport-Security: max-age=31536000');
  header("Content-Security-Policy: frame-ancestors 'self'");
  header('X-Content-Type-Options: nosniff');
});
Apache: hide the versionP-10
# httpd.conf / apache2.conf
ServerTokens Prod
ServerSignature Off
PHP: hide the versionP-10
; php.ini
expose_php = Off
WordPress: hide the generator versionP-10
// WordPress (child theme functions.php)
remove_action('wp_head', 'wp_generator');
add_filter('the_generator', '__return_empty_string');
DNS: DMARC (monitor first)P-14
; DNS TXT record - review the reports first, then tighten step by step
_dmarc.example.jp.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.jp"