Skip to resources
A rendering and indexing experiment · definitely fictional · suspiciously fast delivery
Rendered Eventually / Links
Inspect a page.
Investigate a site.
The tools and the talk behind Rendered Eventually. Compare what the server sends, what the browser renders and what Google reports.
Source HTML→Rendered DOM→Google signals
Choose where to start
One page / Chrome extension
Chrome Page
Inspector
Compare a fresh fetch of source HTML with the rendered DOM of the page you are viewing.
- Spot changes in content, links and metadata.
- Investigate canonicals, robots and structured data.
- Export findings for further review.
Get the Chrome extension ↗
Start with a page open in Chrome. Confirm Google’s indexed state separately in Search Console.
Many pages / Python workflow
Automated analysis
in Google Colab
Move from individual checks to a repeatable investigation across a sitemap or URL list.
- Scan source pages and compare a chosen sample in the browser.
- Add optional Google URL Inspection API evidence.
- Export the report and Excel results.
Open the Colab notebook ↗
Choose File → Save a copy in Drive, then run the setup cell. Google API connection instructions are inside.
The project / brightonSEO talk
The thinking
behind the tools
Diagnosing Rendering and Indexing Issues with the URL Inspection API.
- Understand where source, browser and indexing evidence diverge.
- Explore the investigation workflow.
- See the talk and speaker details.
Read the talk details ↗
Manuel Madeddu · brightonSEO · October 2026