Scrape the page. Collect the evidence.

Point Silkra at a URL and it renders every page, pulls 100+ fields from each one, and flags what's wrong before you open a row.

From one URL to a website you can work with.

Point Silkra at a website and it renders every page, pulls the technical fields, and saves the whole pass, so you can filter it, compare it, and refresh it whenever you need.

  1. See the page as a visitor does.

    JavaScript runs only when a page needs it, and raw HTML is used when it doesn't, so you always get the page a visitor actually sees.

  2. Get the technical record.

    Status codes, indexability, canonicals, headings, links, schema, and the main content come off the same pass and stay attached to the URL, so there are no exports to stitch together.

  3. Come back to it anytime.

    Every scrape is saved, not exported and forgotten. Refresh it later and the new pass sits on top of the last, so you can see exactly what changed.

One row holds the whole page.

Each URL keeps the SEO record you expect, plus what Silkra reads from the rendered page, so columns, filters, and agents all work from the same facts.

Get started
  • Status
  • Title
  • Canonical
  • Indexability
  • Word Count
  • H1
  • Meta Description
  • Rendering Dependence
  • Extraction Coverage %
  • AI Bot Access
  • Closest Neighbor
  • Semantic Group
  • Cannibalization
  • Unique Content %
  • Content Age
  • Title Matches Body
  • First RAG Chunk

Issues flagged as pages land.

Pages are checked against the issue list as they're scraped, from broken canonicals to thin content and missing schema. Each issue arrives with its severity and the pages it affects.

See what AI crawlers actually get.

Many AI crawlers read raw HTML and never run JavaScript. See which pages only fill in after rendering, and the passage an answer engine would quote from each, including when it's buried deep.

Find the pages that matter.

Ask for a topic, a path, or what links where, and the table cuts to that set. Matches are highlighted right in the cells, so you see why a page made the cut.

Know who and what a website talks about.

Silkra sorts the people, organizations, places, and products named on each page and drops the noise. Filter the table by an entity, or hand the list to an agent.

Go past the row.

Open a URL to read what's on the page, see how it links, and check its structured data, all in one panel you can hand to an agent.

Explore the page inspector

Read what a crawler reads.

See the page as clean markdown, or flip to the rendered view. Headings and structure stay intact, so you know exactly what an agent takes away.

# How to run a content audit

A content audit shows where pages overlap, go stale, or drift away from search intent. Use the [SEO audit checklist](/resources/seo-audit-checklist) to review each section consistently.

## Start with a content inventory

Group pages by topic, owner, freshness, and organic purpose. Record which pages attract visits and which sit outside a clear content pathway.

## Evaluate coverage and overlap

Compare pages that serve the same intent, then flag thin resources and guides with no inbound link from a related page.

## Prioritize the next action

Consolidate overlap, strengthen useful pages, and reconnect isolated content.

Review the audit again after the next crawl.

Trace the links in and out.

See what a page links to and what links to it, with placement, relevance, and anchor text for each. Body links stand apart from navigation, so orphans and dead ends are easy to spot.

Verify the structured data.

See the JSON-LD a page declares, types and raw block included, right beside its content, so missing or mismatched markup is easy to catch.

What the scrape is actually for.

Why technical SEO matters for answer engines

Start from the real page.

Answer engines and auditors both have to get the page first. Status codes, JavaScript, robots rules, and template chrome decide whether the body a person sees is actually there to read. If that first pass is thin or wrong, every finding after it is a guess.

A technical scrape gets you the real page: rendered when it has to be, raw HTML when it doesn't, with its fields and links attached. Get that right and your audits, maps, and agent answers all stand on solid ground.

A workspace, not just a scraper.

The scrape is how Silkra collects evidence, not the end product. The crawl becomes a knowledge base you can return to: issues, patterns, links, and the pages behind them, ready for you or an agent to act on.

Maps, search, and agents all work from the same saved pass. Instead of another export, you get a website you can come back to and keep improving.

Create your first workspace.

Turn websites into SEO knowledge bases. Free to start.