FUKAMO GUIDE · Fukamo audit

Scoring methodology

Fukamo calculates scores from evaluated rules and puts content first. Confirmed failures and passes have distinct meanings; reviews take part of the content points, and unavailable checks and non-applicable rules are not counted.

Why might a repeat score fall when I did not change the site?

First establish the number’s scope and available evidence. Then distinguish a confirmed failure, manual review and missing measurement; each state needs a different next step.

When comparing scans, open the PDF reports and compare rule identifiers. A robots.txt change can affect the evidence available for technical SEO; an unavailable speed measurement belongs in a different queue from a confirmed canonical URL defect.

What to do step by step

  1. Levels one to three represent confirmed problem severity.
  2. Level four is manual review without an automatic deduction.
  3. Level five represents a passing rule.
  4. Repeated occurrences do not become separate rule deductions.
  5. SEO and AI views use checks in their respective scopes.

A practical example

The Fukamo score is a weighted mean of five parts: content 35%, Google 15%, AI 15%, technical 10% and experience 25%. Content is earned: a signal gives its weight only when it passes, less when it needs review and nothing when it fails. Thin text holds content low, and the score can stand at most 15 points above content. A page Google cannot index is capped. In the Google and technical parts, failures receive 2.25 times the weighting of passes and a minimum deduction of 4.5 points per weight unit; one area can take at most 20 points. Experience uses the lower performance or accessibility score on the worse measured device. The overall score can exceed it by at most 15 points.

A common mistake

A score is not simply the percentage of checks passed, nor the probability of ranking first. Different tools may use different definitions.

AUDIT OUR OWN WEBSITE

Try the report before checking your site.

Explore the sample report, then enter your own URL to see findings, HTML evidence and a repair plan for your page.

Run your audit

fukamo.com/sk

59/100Your website needs attention.

  • Passed 241
  • To review 17
  • Failed 7
  • Unavailable 8
Search the findings…By severityCSV
  • Critical 0
  • High priority 5
  • Standard priority 2
  • To review 17
  • 01Structured dataHigh priority×2
  • 02SecurityHigh priority
  • 03Performance signalsHigh priority
  • 04PerformanceHigh priority
  • Findings7 to fix241 checks passing
  • Repair plan24 tasks7 fixes · 17 reviews
  • Page data3,243 words10 images without alt
  • Performance and accessibility66 / 100Mobile · Lighthouse
  • Links and server282 links23 external links
Full reportSend by emailCopy linkShare linkBack to site

What do the check statuses mean?

Failed means the available rule’s condition was violated. Review needs human context. Unavailable evidence and an inapplicable check have separate states.

  • Do not interpret a missing performance measurement as a fast page.
  • Do not treat a check for an unnecessary element as a requirement to add that element.

How does a score differ from a task count?

Passed and failed checks with positive weights enter the rule score. Each rule identifier counts once; occurrence counts help establish the repair scope.

  • A hundred occurrences of one defect may need one template edit followed by broad regression checks.
  • Advice with zero weight can still be useful even though it does not change the number.

Which scores can you compare?

The report separates technical areas, content signals, the query and performance. The Fukamo score follows its own rules; it is not a rating assigned by Google.

  • Keep the URL, query, measurement type and available evidence consistent when comparing results.
  • Explain a changed total through specific rules, rather than the point difference alone.

How to prioritise SEO repairs

More severe failures have a larger impact in the methodology. Add page purpose, affected templates and dependencies when deciding the work order.

  • Resolve accidental blocking of a public service page before polishing its wording.
  • After fixing a failure, verify fresh evidence and usability; a high score alone does not establish orders or indexing.

How to verify the result

Use evidence, impact and the recommended fix to decide. Retest rule IDs on the same URL; measure actual search performance and AI citations separately.

Primary documentation developers.google.com ↗

Frequently asked questions

Why might a repeat score fall when I did not change the site?

Compare available inputs, server responses, the exact URL, and rule versions. Dynamic content or rejected requests may change what can be verified. Interpret the score alongside findings; a small point difference does not establish a ranking decline or a worse business.

When the task is complete

Comparisons retain the same scope and explain new or unavailable evidence. Fix decisions follow severity and cause rather than a desire to reach a round number.

Related SEO guides

FROM READING TO YOUR OWN WEBSITE

Check a specific page.

Fukamo shows findings, evidence and the next step.

Start a free audit ↗

836 rules + SEO, AI readability, performance and accessibility measurements for free.

Accessibility checker

FUKAMO / PRIVACY

Your privacy, your control.

These choices cover cookies and browser storage. The audit works just as well without optional storage.

Privacy policy ↗Cookies and third parties ↗