Skip to content
← All integration sources

AwesomeSEO crawler: the data contract.

What the source can contribute, how its records join to the workspace and what is implemented today.

Implementation status

Local implementation

Access and freshness

Read pages from your machine; bearer token authorizes the local crawler.

On demand; the app polls saved crawl state every five seconds.

Fields and useful views

url URL
Page identity and inventory
status HTTP status
Response and redirect inspection
rendered boolean
Actual collection mode
headings Heading[]
Document structure
schemaTypes string[]
Structured data types
fetchedAt timestamp
Evidence age
screenshot path | absent
Captured visual evidence
  • URL inventory
  • Issue groups
  • Heading outline
  • JSON-LD inspector
  • Rendered screenshot

Relations and data quality

crawlId + URL; preserve final URL and canonical as separate observations.

A crawl is bounded by its scope and budget. Rendering is reported per page; a failed renderer must not be described as rendered.

Continue

Related documentation and reading

Filter resources · 1 active

6 of 10 resources shown

Google Search CentralCase studies

Rakuten: recipe structured data

The publisher’s account of a structured data implementation. Reported outcomes belong to that case.

Publisher-reported case
Reference · unreviewed claims
Reading notes
Google Search CentralCase studies

Saramin: investment in SEO

A published implementation case for discussing technical search work and measurement.

Publisher-reported case
Reference · unreviewed claims
Reading notes
Google Search CentralDocumentation

JavaScript SEO basics

Official guidance on crawling, rendering and indexing JavaScript content.

Official reference
Reference · unreviewed claims
Reading notes