Αυτή η μετάφραση δημιουργήθηκε από μηχανή και εκκρεμεί έλεγχος.Μετάβαση στα Αγγλικά
Σε αυτή τη σελίδα

SEO tools: page checks, site crawls and search score

The SEO tools in Backoffice check technical search-engine health on hostnames your workspace owns. You can check one page, crawl a hostname in the background, and follow a score that is recomputed after every completed crawl.

Marketing or web teams run them. A workspace administrator starts checks and crawls; viewers can read the results.

What it is

Availability: Early Access. It has no SLA. Scope and dates can change. The tools are switched on for your organisation when you ask the team.

The tools live in Backoffice under the sidebar group SEO & Marketing: SEO Check, Site Crawls, Search Console and Search Score. Each page works on one domain at a time; pick the domain in the selector at the top of the page.

ToolWhat it does
SEO CheckFetches one page you name and reports a score and a list of issues, most important first.
Site CrawlsCrawls a hostname in the background, within a page budget and the rules of robots.txt.
Site checksWhole-site findings inside a finished crawl: AI-crawler access in robots.txt, llms.txt, address handling, marketing tags and consent tooling, and structured data. See Site checks.
Search ScoreShows the latest score for each crawled hostname and the issues behind it.
Search ConsoleConnects Google Search Console for a domain. See Connect Google Search Console for a domain.

Results are signals for your team to review. They are not a ranking forecast and not a verdict on a site.

Ownership proof

Noxtica fetches only hostnames you can prove you control. It re-checks the proof on every request and never reuses an earlier proof.

ProofWhat it covers
A DNS TXT record published through Backoffice → DomainsThe host and every subdomain. Backoffice labels this “Verified via domain ownership on the Domains page”.
An HTTP file or HTML meta tag proof through Backoffice → DomainsThat exact host only.
A relay hostname whose DNS TXT verification is activeThe whole registered domain (for example shop.example.com proves www.example.com too). Backoffice labels this “Verified via relay hostname (registrable-domain-level)”.
A Search Console Domain property (sc-domain:example.com)The whole registered domain.
A Search Console URL-prefix propertyThe exact host of that property, and nothing wider.

A relay hostname proof is zone-wide, so only verify a relay hostname on a zone you fully control. For relay hostnames, see Content Security Policy, hosts and first-party relay.

Limits you will notice

  • A check fetches the page with a 10-second timeout. Running the same URL again within a minute returns the cached result.
  • Checks and crawls are each limited to 30 requests per 60 seconds for your workspace.
  • A crawl stops at a page budget. The default is 40 pages and the platform bounds it between 10 and 90. Backoffice shows “N of M pages” for each crawl, so the budget in force is visible. Crawls do not promise to cover every reachable page.
  • Crawls honour robots.txt for the product token noxtica, and honour a Crawl-delay of up to 10 seconds.

Site checks

A finished crawl adds findings that apply to the whole site rather than to one page. Open the crawl and read Site checks.

CheckWhat it reports
AI-crawler accessHow your robots.txt treats crawlers that collect content for AI products: blocked, allowed, partly restricted, conflicting rules, or not named (the crawler then follows your rules for all crawlers, which may allow or block it). It also lists Content-Signal directives found in robots.txt.
llms.txtWhether the site serves an llms.txt file, and its size when found.
Address checksWhether http:// redirects to https://, whether the www and non-www addresses are served as one site, and whether a made-up address answers with a proper error.
Marketing tags and consentWhich marketing and analytics tags appear in the page HTML (for example Google Tag Manager, Google Analytics 4, Google Ads, Meta Pixel, LinkedIn Insight Tag, Microsoft Clarity, HubSpot), whether a consent-management platform script or a Google Consent Mode default appears, and whether more than one Google Tag Manager container loads.
Structured data (JSON-LD)How many crawled pages declare structured data, which types, and how many blocks cannot be read.

These checks read robots.txt, llms.txt and the static HTML of each page. Tags that a tag manager or consent platform adds at runtime are not visible. robots.txt is a request to crawlers, not access control. The checks do not measure whether any AI product cites or ranks your pages.

Prerequisites

  • Role: viewer or higher to read results; administrator to run a check, start a crawl or connect Search Console. Running a check or a crawl does not ask for step-up MFA; connecting Search Console does.
  • SEO checks enabled for your organisation. If they are not, Backoffice shows “SEO checks are not available right now”.
  • Site crawls enabled for your organisation. Without them Backoffice shows “Site crawls are not available in this environment yet”.
  • A hostname you own, with one of the proofs above.
  • The domain added to your workspace under Backoffice → Domains. See Domains, site keys and the install card.

Steps

1. Prove ownership of the hostname

Choose one:

  • Backoffice → Domains: verify the domain with a DNS TXT record, HTTP file or HTML meta tag.
  • Backoffice → Integrations & API → Relay Hostnames: add and verify a relay hostname on your domain.
  • Backoffice → SEO & Marketing → Search Console: connect a verified Search Console property for the domain.

Without a proof, checks and crawls answer “Verify hostname ownership first”.

2. Run a single-page check

  1. Backoffice → SEO & Marketing → SEO Check.
  2. Choose the domain. The Page URL field is pre-filled with https://<your-hostname>/.
  3. Enter the full URL of the page, for example https://example.com/pricing.
  4. Press Run check.

The result shows the score, the HTTP status, when the check ran, and how the hostname was verified. Issues are listed with their severity and guidance. The “Recent checks” list below keeps earlier runs with their scores.

A check reviews title and meta description, headings, indexability and canonical tags, images, structured data, security headers, language and viewport tags, and time to first byte.

3. Fix the issues and run the check again

Fix the page on your site and press Run check again. If you check the same URL within a minute, you see the cached result; wait a minute for a fresh fetch.

4. Start a site crawl

  1. Backoffice → SEO & Marketing → Site Crawls.
  2. Choose the domain and enter the Hostname to crawl, for example example.com.
  3. Leave Also check pages my robots.txt disallows off unless you need those pages checked. When ticked, Noxtica fetches disallowed pages too and still reports them as “Blocked by robots.txt”. The choice is written to the audit log.
  4. Press Start crawl.

The crawl is queued and runs in the background. The Crawl history shows each run with its status: Queued, Running, Partial, Complete or Failed. A Partial run stopped because of a platform time or request budget and resumes on a later run. A crawl that reaches its page budget is marked Complete even when more pages exist. A crawl re-checks ownership each time it resumes and fails if the proof no longer holds.

The crawl starts from your hostname and from its sitemap, follows internal links, and stays inside the hostname. If the proof covers the whole registered domain, its subdomains are in scope too. It never widens its scope while running.

5. Read the crawl

Open a crawl in the history. The detail view lists the pages (with HTTP status, canonical URL, and badges for noindex and “robots.txt blocked”, and how the page was discovered: Seed URL, Sitemap or Internal link) and the issues found, each marked Site-wide or Page.

6. Follow the search score

Backoffice → SEO & Marketing → Search Score. The page shows the latest daily rollup for each crawled hostname: the mean technical score across the pages the crawl fetched, plus that day’s issue counts by severity. Open a hostname to see the issues behind its score. A new rollup appears after each completed crawl. Until a crawl has completed the page says “No score rollup yet”.

7. Get alerted when the score drops

Create an alert rule from the SEO score or SEO issue templates. See Uptime checks, alerts, status reports and the status page.

Verify it works

  • A check returns a score from 0 to 100 and an issue list. Each page starts at 100. For each distinct issue code, Noxtica takes off 25 points for a critical issue, 10 for a warning and 2 for an info issue, and never goes below 0.
  • If the page could not be fetched, the check shows no score and a message that names the failure class (see Troubleshooting).
  • A crawl row moves from Queued to Running and ends at Complete or Partial, with “N of M pages”.
  • Search Score lists your hostname with a score and a “Computed” time once a crawl completes.

Example issues, by severity:

SeverityExamples (issue codes)
CriticalSEO_STATUS_4XX, SEO_STATUS_5XX, SEO_TITLE_MISSING, SEO_H1_MISSING, SEO_NOINDEX_UNEXPECTED, SEO_SITE_WIDE_NOINDEX, SEO_VIEWPORT_MISSING
WarningSEO_REDIRECT_CHAIN_LONG, SEO_TITLE_LENGTH_OUT_OF_RANGE, SEO_META_DESCRIPTION_MISSING, SEO_CANONICAL_MISMATCH, SEO_ORPHAN_PAGE, SEO_IMG_ALT_MISSING, SEO_TTFB_SLOW
InfoSEO_ROBOTS_BLOCKED, SEO_META_DESCRIPTION_LENGTH_OUT_OF_RANGE, SEO_STRUCTURED_DATA_ABSENT, SEO_OG_TAGS_ABSENT, SEO_SECURITY_HEADER_MISSING

Troubleshooting

SymptomCauseFix
“Verify hostname ownership first”No active proof (Domains verification, relay hostname or Search Console property) covers the hostnameComplete step 1. A URL-prefix property covers its exact host only; use a Domain property or a relay hostname for subdomains.
“Too many checks” or “Too many crawl requests”More than 30 requests in 60 secondsWait a minute and try again.
“Enter a valid page URL” or “Enter a hostname like example.com”The URL or hostname is malformedEnter a full URL with https:// for checks, and a bare hostname for crawls.
“SEO checks are not available right now”SEO checks are not enabled for your organisationAsk your account team.
“Site crawls are not available in this environment yet”Crawling is not enabled for your organisationAsk your account team.
Check shows “The page took too long to respond”The page did not answer within 10 secondsMake sure the server responds quickly, then run it again.
Check shows “This page cannot be checked because its address is not a public website address”The URL resolves to a private or internal addressUse a public https:// URL.
Check shows “Your domain’s DNS changed during the check”DNS changed while the check ran, so it stopped for safetyKeep DNS records stable and run the check again.
Check shows “The page returned an error status”The page answered 4xx or 5xxFix the page, then run it again.
Crawl shows fewer pages than you expectedThe page budget was reached, robots.txt disallows pages, or robots.txt could not be fetchedCompare the “N of M pages” count with your site size and check your robots.txt. A host whose robots.txt answers with a server error or a network error is not crawled in that run.
Crawl is FailedOwnership proof lapsed while the crawl was resumed, or a temporary faultRe-establish the proof and start a new crawl.
Search Score says “No score rollup yet”No crawl has completed for the hostnameStart a crawl and wait for it to complete.

Who it fits

Marketing and web teams that own a public site and want a repeatable technical read on it: what blocks indexing, how robots.txt treats AI crawlers, whether llms.txt and structured data exist, and which marketing tags load. Administrators run the checks. Viewers read the results, and the AI Assistant and the MCP server can read them with the same permissions.

It does not fit teams looking for keyword research, rank tracking, backlink data, broken-link (link liveness) checking, real-user Core Web Vitals data, content writing, email sending or outreach, or campaign tools. None of those is part of this product.

Limits

  • Early Access: no SLA, and scope and dates can change.
  • Only hostnames you have verified as yours. The proof is re-checked on every request.
  • A check fetches one page with a 10-second timeout. A crawl stops at a page budget and does not promise to cover every reachable page.
  • Crawls follow robots.txt for the product token noxtica. An administrator can opt in per crawl to also fetch disallowed pages on a domain they own; the choice is audit-logged and those pages are still reported as blocked.
  • Results are signals, not a ranking forecast or a verdict on a site.
  • Answer-engine readiness checks (AI-crawler access, llms.txt, structured data) report what your site exposes. They do not show whether an AI product cites or ranks your pages.
  • Checks and crawls read static HTML and do not run JavaScript. Content, tags or structured data added at runtime are not seen.

Common questions

Is there an AEO (answer-engine optimisation) score?

No. The score is a technical SEO score, the mean over the crawled pages. The answer-engine readiness checks are separate findings: AI-crawler access, llms.txt and structured data coverage.

Can it send email or run campaigns?

No. It reads your site and reports findings. It does not send email, write content or run campaigns.

Who can run a check?

An administrator runs checks and crawls. A viewer reads results. Running a check or a crawl does not ask for step-up verification; connecting Search Console does.

Does it show Core Web Vitals?

No. Real-user (field) Core Web Vitals data is not part of this product. A check reports time to first byte from its own single fetch.