Domain SEO Overview: Metadata, Sitemaps & Keywords

One run answers one question: is this site technically ready to be found, and what should be fixed first?

It returns a seo_readiness score from 0 to 100, a severity-ordered findings list where every item names the signal it came from, and the evidence behind each one: the title and meta description as actually served, robots.txt, /llms.txt, and the sitemaps the site really publishes.

Evidence from an owner run, not a customer result: linear.app returned seo_readiness: 100 with an empty findings list. github.com returned 90 with title_too_long and meta_description_too_long. GitHub answers 406 on /sitemap.xml, so a checker that only tries that path reports "no sitemap"; this Actor reads robots.txt, finds https://github.com/sitemap_marketing.xml, and reports 376 URLs from it.

Build a Domain SEO Overview from public website evidence: page metadata, sitemap observations and keyword suggestions. Use it to inspect a site before a technical SEO audit or competitor review.

Start with a verified example

Open the Python quickstart. Includes a runnable one-target input, actual owner-run output from October 28, 2026, Python with an explicit spending cap, and source limits. Owner tests are not customer outcomes.

{
  "domains": [
    "linear.app"
  ],
  "top_keywords": 0,
  "competitors": 0,
  "use_paid_upstream": false
}

The example cap is $0.03 in event charges, not a quoted run price. Review the live Pricing tab. The guide does not run the Actor or request your token.

What you get

• Inspect the page title and meta description of a domain.

• Check sitemap availability and inspect the URLs it lists. /sitemap.xml, /sitemap_index.xml and any sitemap URL declared in robots.txt are checked, so a sitemap published at a non-standard path is still found.

• Read robots.txt and /llms.txt: whether a crawler is shut out of the whole site, and whether the site publishes an AI-crawler brief (llms_txt_present, llms_txt_bytes).

• Get a findings list of what to fix, ordered by severity, plus a seo_readiness score from 0 to 100. Every finding names a signal observed in that run; nothing is inferred from a missing one.

• Collect available Google Autocomplete keyword suggestions with explicit source and availability fields.

• See how popular the site is in Chrome: a popularity_tier such as top_10k or top_100k, from the monthly Chrome UX Report (Google) top-origins list.

Quick start

Edit the sample target in Apify Console, or pass an explicit target through the API:

{

  "domains": [

    "linear.app"

  ],

  "top_keywords": 0,

  "competitors": 0,

  "use_paid_upstream": false

}

Results are written to the default dataset. Use the overview dataset view to inspect records and export available columns as JSON, CSV or Excel.

Captured output example

Selected fields from an earlier validation run; these values are not current measurements.

{

  "domain": "github.com",

  "http_status": 200,

  "public_page_available": true,

  "page_title": "GitHub · Change is constant. GitHub keeps you ahead. · GitHub · GitHub",

  "meta_description": "Join the world's most widely adopted, AI-powered developer platform where millions of developers, businesses, and the largest open source community build software that advances humanity.",

  "sitemap_present": true,

  "sitemap_kind": "urlset",

  "sitemap_source_url": "https://github.com/sitemap_marketing.xml",

  "sitemap_urls_found": 376,

  "robots_txt_present": true,

  "robots_blocks_all": false,

  "robots_sitemap_refs": 1,

  "llms_txt_present": true,

  "llms_txt_bytes": 28658,

  "seo_readiness": 90,

  "findings": [

    {

      "code": "title_too_long",

      "severity": "low",

      "message": "The title is 70 characters; roughly 60 is what a search result shows."

    },

    {

      "code": "meta_description_too_long",

      "severity": "low",

      "message": "The meta description is 186 characters; roughly 160 is what a search result shows."

    }

  ],

  "metrics_available": false,

  "organic_traffic_estimate": null,

  "provider_mode": "native"

}

What the dated example returns (verified 2026-10-31)

The block above is the real output of run hcrUbtsDkyQgtxkcc on build 1.2.2, trimmed to the new fields. Note what it demonstrates: sitemap_source_url is sitemap_marketing.xml, a path declared in robots.txt and not one of the default paths, so the sitemap is found rather than reported missing.

seo_readiness starts at 100 and subtracts 30 for a high-severity finding, 15 for medium and 5 for low, so this run scores 90 for two low findings. It is null when the homepage could not be read: a score of 0 for an unreadable page would say "your site is bad" when the truth is "we saw nothing".

Sources and coverage

popularity_tier is the Chrome UX Report rank bucket of the site's origin, based on Chrome page loads (source: Chrome UX Report by Google, monthly; popularity_source names the month). It is not a visit count, not traffic and not a Google ranking. null means the site is not in the list or the list was unavailable.

Public mode does not measure organic traffic, ranking positions, search volume, CPC or indexed-page counts. Those fields remain null when unavailable. Sitemap URL counts are not Google index counts, and autocomplete order is not a search ranking.

The default uses public or platform-native sources with external paid data providers disabled. Apify Actor events and platform usage are separate from external API costs. Unsupported or unavailable fields are reported honestly; this is not a guarantee of complete source coverage.

Pricing

Public/native mode does not emit domain-lookup or domain-result events. The Actor start event still applies. The database lookup/result rates below apply only when their eligible paid-data mode is explicitly enabled. Published standard event rates (before plan discounts):

| Event | USD per event | Meaning |

|---|---:|---|

| apify-actor-start | $5e-05 | Actor Start |

| domain-lookup | $0.02 | Domain lookup |

| domain-result | $0.005 | Domain result |

Startup events, when configured, are separate from result events. Result-event charging follows the Actor's eligibility and useful-output rules; public fallback or diagnostic outputs may be uncharged. The live Pricing tab is authoritative. Set a maximum total charge before starting a run.

API, MCP and workflow integrations

Actor ID: hirepulse/domain-seo-overview. Run this Actor through Apify API or its official client libraries. Connect it to n8n or Make using the Apify integration, or expose it to AI agents through Apify's MCP server. This Actor does not host its own MCP server. API calls must supply the required target; Console prefill is an editable example, not a hidden API target.

Use cases and data coverage

| Dimension | Coverage |

|---|---|

| Use cases | Website SEO audits, competitor website research and brand monitoring |

| Target sources | Company websites, public sitemaps and Google Autocomplete |

| Output | Structured JSON records in an Apify dataset |

Store categorization is assigned by Apify. No search position, AI recommendation, completeness or fixed runtime is guaranteed.

Related HirePulse tools

• Keyword suggestions
• Website technology signals
• Public crawler readiness