A screenshot can show that a heading looks right. It cannot prove which content a crawler received or whether the page is allowed in search. Review the visual page and the technical response as different pieces of evidence.
Begin with a public service page
Open the page normally and read its title, main heading, service details, location information, and contact path. Note which important facts appear only inside images.
Our Russco case study pairs project and equipment photography with service writing. The photographs support the explanation rather than carrying the only description of the work.
Inspect the response and rendered content
Ask the developer to check the response status, page source, rendered text, and indexing controls. A page dependent on scripts may need both the original HTML and the completed browser view inspected.
Check normal links to the page as well. A useful page that is difficult to discover inside the site needs a navigation review, not just more text.
Check controls in their proper place
Robots rules, noindex directives, canonical URLs, and host-level access rules do different jobs. Document the actual finding instead of describing all of them as an “AI block.”
For Google’s AI features, the relevant requirements are documented in its search guidance. ChatGPT search has separate crawler documentation. Use the guidance for the product you are checking.
Avoid overstating the test
A public browser check is not a crawl from every provider’s network. Reading returned HTML does not reproduce a model’s internal understanding. State those limits when reporting the result.
Our SEO service combines access checks with the page improvements customers can see. Fix the observed problem, then verify that specific change.
What each inspection can tell you
Browser view: shows what a visitor sees in that browser. Page source: shows the initial HTML returned. Rendered page inspection: shows the document after the browser has processed scripts. Search Console URL Inspection: provides information about Google’s recorded or tested version, depending on the view you choose.
Compare the service name, coverage, important limitations and contact link across the relevant views. If those facts appear only in a picture, supply accessible text. If scripts supply them, investigate rendering and access rather than assuming the initial source alone proves the page is empty.
Document a concrete finding such as “the service description is present in the rendered page but not the initial HTML.” That is evidence for a developer to investigate. “This is what every AI sees” is not a conclusion these checks support.
I run Good Creations in Grants Pass. I work directly with business owners on website design, content, and search. My work includes service writing, inventory websites, and custom publishing tools.
Meet Bob ↗
