How can I justify priorities without inventing revenue forecasts?
Combine confidence in the evidence, template reach and business relevance. An access problem on a major service page is different from a suggestion on an obsolete archive.
What to do step by step
- Check the scope and origin of the data.
- Record indexing intent and page purpose.
- Group findings by shared cause.
- Separate a straightforward fix from an experiment.
- Agree on a review date and comparison metric.
A practical example
Noindex can be appropriate on a cart and harmful on a primary service page. The instruction must reflect purpose, not just the same word in a report.
A common mistake
A score does not predict revenue or ranking. If evidence is missing for an area, say what must be obtained instead of declaring success.
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/skSeptember 16, 2026
59/ 100
HTML response size · Fukamo 200 kB budget
- Evidence
- 314476 bytes of decoded HTML; this is not the transferred compressed size.
- Repair
- Reduce unnecessary HTML and inline data. The 200 kB threshold is a Fukamo budget, not a Google limit or compressed transfer size.
Inline JS size · Fukamo 64 KiB budget
- Evidence
- 4 blocks; 179621 bytes before transfer compression.
- Repair
- Reduce inline data exceeding the Fukamo 64 KiB budget. Compare an external cacheable file and measure the impact.
ImageObject · basic data
- Evidence
- 1 entity. Missing data ImageObject #1: contentUrl.
- Repair
- Check appropriate properties for this type. Checking a selected set does not replace complete validation or establish rich-result eligibility.
Illustrations have the context they need
- Evidence
- 1 of 1 figure element has no text figcaption.
- Repair
- Add a caption where the image needs explanation. Figcaption is optional and does not replace alt.
What an audit proves and what needs interpretation
A noindex instruction is an observation. Calling it a defect requires knowing that the owner wants this page in search results.
- Fact — the response contains the instruction.
- Interpretation — it conflicts with the service page’s purpose.
- Recommendation — change its source and retest the public URL.
How to prioritize findings by confidence and impact
A severity label alone does not create an executable plan. Combine verified cause, important affected pages and dependencies.
- Confirm reach from an inventory or shared implementation.
- Label effort estimates that still need developer input.
- Assign the person who can supply missing business facts.
When is an SEO recommendation an experiment?
A repaired link has a testable destination. Rewriting service copy to improve inquiry quality is a hypothesis requiring a baseline and observation period.
- Define what a qualified inquiry means.
- Keep clicks, submissions and orders separate.
- Record pricing, campaign and capacity changes.
How to report verified SEO changes and remaining questions
Show work completed, observed effect and uncertainty independently. A technical score is one input to consulting judgment, not a revenue forecast.
- Verify the agreed public behavior.
- Review the business metric through its actual data source.
- Update priorities when new evidence changes the original assumptions.
How to verify the result
Use the scoring methodology to interpret automated findings, then document the page’s business purpose. Verify the repair immediately and review its business indicator on the agreed date.
Primary documentation developers.google.com ↗
Frequently asked questions
How can I justify priorities without inventing revenue forecasts?
Separate evidence confidence, affected scope, and commercial importance. A blocker on a sales page can outrank dozens of cosmetic issues. State assumptions and ownership when estimating effort. A growth percentage without baseline data does not help planning.
When the task is complete
The client understands the ordering and which assumptions need validation. Measure technical resolution separately from business outcomes.
Related SEO guides
Check a specific page.
Fukamo shows findings, evidence and the next step.
836 rules + SEO, AI readability, performance and accessibility measurements for free.