Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Custom structured data extraction with JetOctopus

Updated · 7 min read

Short answer JetOctopus reads the schema markup on every page it crawls and shows which types you use, which pages have none and which carry the wrong type. Custom extraction pulls one field, like author or phone, into a column. Its smallest plan costs US$349 a month or more, so most small sites are better served by Google's free checks.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What JetOctopus finds in your structured data

Structured data (schema markup) is code that labels facts on a page, such as your business name, an article's author or a product's price, so search engines read them without guessing. JetOctopus is a cloud crawler: it visits every page of your site and records what it finds. For schema it does two jobs. Steps below follow JetOctopus's own guides and product posts, read November 2026; menu names may have moved since.

JobWhere in JetOctopusWhat it answers
Inventory of all schemaExtraction dashboard > Structured Data ExtractionWhich types you use, on how many pages, which pages have none
One field from every pageCrawl settings > Custom ExtractionIs `author`, `telephone` or `dateModified` filled in, and with what?
Rendered vs raw pageJavaScript crawl, then compare JS vs non-JSDoes the schema exist before scripts run?

JetOctopus's 2023 launch post says the structured data report needs no extra crawl settings and lists four uses: find pages without structured data, find pages with irrelevant structured data, see how types are spread across the site, and analyze the fields inside each type.

What it doesn't settle on its own: whether Google will use the markup. Confirm that with Google's tools (Step 4).

Do you need JetOctopus for this?

Usually not, if your site has a few hundred pages. JetOctopus is built for large sites; its pricing page calls it a platform "built for large websites, e-commerce catalogs, and the agencies that manage them."

OptionCost (November 2026)CoversLimit
JetOctopus Growth planUS$349 or US$459 a month, by billing term (annual saves 25%); €299 or €399500,000 crawled URLs a monthTrial only after a sales demo; no Canadian-dollar price
Google Search ConsoleFreeRich result reports for your verified siteOnly types Google shows as rich results
Rich Results TestFreeOne URL or code snippet at a timeGoogle-supported types only
Schema Markup Validator (schema.org)FreeOne URL or snippet, every schema.org typeChecks vocabulary, not Google eligibility

The pricing page says the trial needs no credit card: "we open your trial account after the demo."

A small site has three or four page templates (home, service, location, blog post). Schema almost always comes from the template or a plugin, so testing one page per template in the Rich Results Test covers the site. A crawler earns its price when you have thousands of pages, several templates built by different people, or markup that changes with stock or prices.

Step 1: Crawl the site, with JavaScript if your schema needs it

Start a new crawl of the whole site. If your schema is added by a plugin script, Google Tag Manager or a page builder that writes it in the browser, tick Execute JavaScript in the basic crawl settings. JetOctopus's extraction guide says it reads plain HTML unless that box is on.

Google can read schema written by JavaScript; its documentation names Google Tag Manager and custom JavaScript as common ways to generate it. Many other crawlers can't. JetOctopus's 2026 audit guide suggests the Compare JS vs non-JS report to see which elements, schema included, exist only after scripts run. More on that: JavaScript SEO audit.

Step 2: Read the Structured Data Extraction report

Open the Extraction dashboard and choose Structured Data Extraction. Read it in this order:

  1. Pages without structured data. Sort by folder. A missing type on one service page is a slip; missing on all of them is a template.
  2. Type spread. Each type, such as Organization, LocalBusiness, Article or BreadcrumbList, with its page count. Look for the wrong type on a page: Article on a service page, Product on a blog post.
  3. Fields. Open a type to see which properties each page carries and which are empty.
  4. One page in detail. Since July 2024 the URL Explorer shows the structured data of a single URL.

The launch post describes the extraction as pulling structured data "in JSON format". If your site uses Microdata (schema written into the HTML tags), check that one known page shows up before trusting the totals.

Step 3: Pull one field from every page with custom extraction

When you need one value side by side across all pages, such as the phone number in every location page's schema, set up a rule:

  1. In the crawl settings, open Custom Extraction and click + Add Rule. Each crawl takes up to 50 rules.
  2. Give the rule a clear title and pick a type: CSS, regex (a text pattern), XPath (added July 2024) or JavaScript run on the rendered page (added August 2024).
  3. To grab whole JSON-LD blocks, a CSS rule such as `script[type="application/ld+json"]` with the action Get All and data type Text is a starting point. To pull one field, use a regex or JavaScript rule instead.
  4. Click Test This Rule on a real URL before crawling. JetOctopus's guide says to check every rule this way, since some sites serve different code to different browsers.
  5. After the crawl, read Crawler > Custom Extraction for counts, or Data Tables with the Custom Extraction filter to see the value in a column. Export to CSV, Excel or Google Sheets.

The extractor reads only pages that return a 200 status (a normal, working page).

Then compare the column with what visitors see. Google's rule:

"Don't mark up content that is not visible to readers of the page." (Google Search Central: General structured data guidelines)

An old phone number in the schema and a new one in the footer is a common find after a redesign.

Step 4: Confirm errors with Google's own tools

A crawler tells you what is there. Google decides what counts. For each template with a problem:

  1. Paste one URL into Google's Rich Results Test. It lists errors (a required property missing) and warnings (a recommended one missing). Google says items missing required properties "are not eligible for rich results."
  2. For types Google doesn't show as rich results, use the Schema Markup Validator to check the code is well formed.
  3. After the fix goes live, watch Search Console. Google says to use the Rich Results Test during development and "the Rich result status reports after deployment". Where to find them: Search Console for a small business.

Keep expectations level:

"Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test." (Google Search Central: General structured data guidelines)

Some types no longer show at all. FAQ rich results stopped appearing in Google Search on May 7, 2026, per Google's documentation updates log. Which ones still show: schema for rich results.

What to fix first

  1. Schema that contradicts the page: wrong phone, old address, a price that changed. It misleads people and breaks Google's rules.
  2. Required properties missing on a type Google still shows. Usually one template edit fixes every page.
  3. Wrong type on a page. Replace it with the most specific type that fits.
  4. Missing schema on key pages: home, location and service pages.
  5. Recommended properties you can fill truthfully. Least urgent.

Several types on one page are fine. Google's guidelines say it understands multiple items on a page, nested or listed separately. The problem is irrelevant markup, not the number of types.

Example

Illustrative cases with invented round numbers.

A home services firm with 60 pages (US dollars)

The owner tests one page from each of four templates in the Rich Results Test. The location template is missing the address in its LocalBusiness markup. One template fix covers 20 pages; Search Console shows them valid two weeks later. Cost: $0.

A parts retailer with 40,000 product pages (Canadian dollars)

Prices change daily. A JetOctopus crawl shows Product schema on 31,000 pages and none on 9,000 that were built from an older template. A custom extraction rule on availability finds 1,200 pages whose schema says in stock while the page says sold out. The Growth plan is billed in US dollars or euros, so its Canadian cost moves with the exchange rate. At 40,000 pages, the crawl earns its price.

FAQ

Does JetOctopus validate schema against Google's rules?

It flags schema types and markup errors, but its own guides say to validate in Google's Rich Results Test. Confirm one page per template there.

Is there a free way to extract schema from every page?

Search Console's rich result reports cover your whole site for types Google shows. For others, test one page per template in the Schema Markup Validator.

Do I need JavaScript crawling?

Only if a plugin, tag manager or page builder adds schema in the browser. If it's in the page source, a plain crawl reads it.

Does more schema mean better rankings?

No. Markup makes a page eligible for rich results, nothing more. Google says even a structured data manual action "doesn't affect how the page ranks."

Different for you?

Keep learning

NextAhrefs technical SEO audit: run Site Audit and read the resultsHow to set up Ahrefs Site Audit for your own website, what Health Score and errors really mean, which issues to fix first, and what the free account covers.

Ask us one question

One line is enough. We reply by email.

Sources

  1. JetOctopus: Product update, structured data extraction (June 2023)
  2. JetOctopus: Custom extraction guide with multiple use cases
  3. JetOctopus: Sum up for 2024 (XPath and JavaScript custom extraction)
  4. JetOctopus: Technical SEO audit for Google and AI search (August 2026)
  5. JetOctopus: Ecommerce SEO audit checklist
  6. JetOctopus: Plans and pricing
  7. Google Search Central: General structured data guidelines
  8. Google Search Central: Introduction to structured data markup
  9. Google Search Central: Generate structured data with JavaScript
  10. Google Search Central: Latest documentation updates
  11. Google: Rich Results Test
  12. Schema.org: Schema Markup Validator