Do we have to change our templates?

Why the audit runs per template

Your site has a handful of templates and thousands of URLs, and the fixes ship per template. So the audit takes one representative URL for each: a blog post, a product page, a category page, a landing page. Each URL is checked against the 21 things that decide whether a page can be retrieved and cited, and each check comes back pass, warn, or fail with the value that tripped it. A fail on the blog template is a fail on every post; a pass on the product template is a pass on every product.

What the fix list looks like

The list is written per template, for the team that owns it, with the check and the value that failed:

• The blog template renders its body client-side, so the engines get an empty shell.
• The product template has no meta description.
• A robots.txt rule blocks two AI crawlers site-wide, a one-line fix with a site-wide effect.

Some findings are site-wide rather than per template, robots.txt and llms.txt among them, and those tend to be the smallest changes with the widest reach. Your platform team decides the order, and on Managed GEO our team ships the fixes instead.

How you know the work landed

After a fix ships, the same URL is audited again. A check flipping from fail to pass is the proof that the change reached the page, independent of anything an engine does with it. Whether that template then starts being cited is a separate question, answered by the daily runs: the cited-pages table shows which of your URLs win which prompts, and it moves in its own time rather than on a date we set.