Why do some findings have no marked page element?
The preview supports orientation; it is not a complete working copy of the website. Content requiring interaction or login needs separate testing. Head declarations have no visible content position.
What to do step by step
- Enter the main search phrase, then follow the preview and analysis.
- Review attention items in the scanner panel.
- Separate confirmed issues, manual reviews and passed checks in the report.
- Open a marker or item to inspect its evidence.
- Use the final verdict and PDF action sections after completion.
A practical example
An image alternative can relate to a visible element. A meta description is a head declaration and is presented as code-level evidence. Both have detail, but only one has a visual target.
A common mistake
The scanner animation is not a live simulation of Googlebot. It presents progress and helps explain the available checks.
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 does a finding marker show?
A visual finding connects a check with a place on the page. The rule detail explains the property to inspect; a coloured outline alone cannot determine the right edit.
- For an image, inspect its HTML and decide whether it conveys information or is decorative.
- For a heading, compare its text, H1–H6 level and purpose within the section.
Why does the preview differ from the live site?
The audit preview helps you navigate the fetched content. Original scripts do not run there as they do on the live site, so an interaction-generated element may be absent.
- Test dropdown menus, sign-in and checkout completion on the original website.
- Compare JavaScript-generated content with the separate rendered evidence when that measurement is available.
Where to find issues without a visible element
Canonicals, meta descriptions and HTTP headers belong to the document or server response. Their evidence remains available in the detail even without an outlined element.
- For a head declaration, inspect the complete element, including its value and destination URL.
- For a response problem, record the status and redirects; scrolling the preview cannot explain them.
What does the scan animation show?
Scan playback reveals available findings progressively. The scanner position is an interface feature; it is not an observation of Googlebot visiting your server.
- Pause playback, open a finding and inspect its evidence.
- After a fix, compare the HTML property. A position shift caused by viewport width alone does not establish a regression.
How to verify the result
If a marker position differs from the original page, inspect its evidence. Responsive or dynamic layouts can change geometry; the HTML property is the basis for a fix.
Primary documentation developers.google.com ↗
Frequently asked questions
Why do some findings have no marked page element?
Metadata, response headers, and robots.txt have no visible position inside the page. Attaching them to a random element would be misleading. They belong to the code layer with their source explained. An image marker identifies its location, not necessarily the entire cause of the issue.
When the task is complete
The detail distinguishes visible elements, code, and supporting responses. Markers stay attached during scrolling, and the finding opens with readable evidence.
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.