Search Engine SeerLog in

Visual journey

Before and after our own fixes

The six fixes our audit found on this site, one by one, and what we will measure after launch.

Every number comes from our own recorded runs. The first diagram is labelled where an example is used.

79Audit score beforemeasured 2026-10-10SpeedSelf-hosted fonts and a static pageCanonical linkOn every pageStructured dataWritten by our generatorSocial tagsOn every pageSitemapLists every pageSecurity headersSet in the server configFixes in this buildA count of changes made, not a score?Audit score after launchpending the re-auditAI answer checks by week.Unchanged until engine access changes.
Step 1 of 8

Where we started

What it checks. The old home page, 2026-10-10.

What we found. Score 79, grade B. Six findings. The AI answer checks (grid, bottom left) show which engines could be asked each week.

What to do. Fix the findings in order.

Step 2 of 8

Fix 1: speed

What it checks. Audit finding 1 of 6.

What we found. Self-hosted fonts and a static page. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 3 of 8

Fix 2: canonical link

What it checks. Audit finding 2 of 6.

What we found. On every page. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 4 of 8

Fix 3: structured data

What it checks. Audit finding 3 of 6.

What we found. Written by our generator. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 5 of 8

Fix 4: social tags

What it checks. Audit finding 4 of 6.

What we found. On every page. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 6 of 8

Fix 5: sitemap

What it checks. Audit finding 5 of 6.

What we found. Lists every page. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 7 of 8

Fix 6: security headers

What it checks. Audit finding 6 of 6.

What we found. Set in the server config. This is a change in the build, checked in the release files.

What to do. Re-measure after launch.

Step 8 of 8

What we will measure after launch

What it checks. The same audit, run again on the live site.

What we found. Not measured yet. The ring on the right stays empty until the result is in.

What to do. We replace this page with the new score and the new AI answer counts.

Next step

Pick one.

Run the quick check on your siteRead the sample reportHold a place at launch