Audit generated SEO pages
Re-checks the generated pages of the organization (or one `collection`) against their rules and returns per-page findings: an empty title or description, a rule that was deleted or deactivated, templates changed after the page was rendered (the page is stale), and the robots directive the page deserves. Findings are advisory — nothing is rewritten; run `generateSeoPages` to fix what the audit found.
Операция для полного ключа
Re-checks the generated pages of the organization (or one collection) against their rules and returns per-page findings: an empty title or description, a rule that was deleted or deactivated, templates changed after the page was rendered (the page is stale), and the robots directive the page deserves. Findings are advisory — nothing is rewritten; run generateSeoPages to fix what the audit found.
Authorization
api_key_header Every request carries an organization API key. A key has one of two scopes. A full key reaches every operation in this document and belongs on your server. A search key is the one to ship in a browser widget or a storefront page: it reaches only the operations marked x-nova-key-scope: search — searching, federated search, recommendations, event ingestion, and the visitor-facing AI operations (semantic and image search, voice transcription and voice search, assistant chat, and the visitor's own conversation). It cannot write documents or read or change configuration; any other operation answers 403. AI operations are paid in credits from the organization's wallet whichever key calls them (402 when the balance runs out), and a search key needs X-NOVA-SESSION-ID on them: the session is what a conversation belongs to, and what the per-session allowance (429) is counted against. A key of either scope may additionally carry restrictions set in the console: an allowlist of collections (403 elsewhere), a forced filter_by per collection that is ANDed into every search (document-level access control), an allowlist of fields (include_fields is limited to it and a request naming any other field in query_by, facet_by, sort_by, filter_by or highlight_fields answers 400), an IP/CIDR allowlist and an Origin/Referer allowlist (403), and a per-key rate limit (429 with Retry-After).
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/seo/pages/audit" \ -H "Content-Type: application/json" \ -d '{}'{ "checked": 0, "findings": [ { "page_id": "string", "url": "string", "robots": "index", "issues": [ "string" ] } ]}Bulk-generate SEO pages for a collection POST
Renders every active rule of the collection (or just the one `rule_id` names) against the live index: the engine's facet counts for the rule's `facet_field` supply one page per value, with `#COUNT#` set to the number of documents carrying it. Pages for values that already exist are re-rendered in place; the rest are created. The response is the generation report — list the pages themselves with `listSeoPages`.
Export a sitemap of the generated SEO pages GET
The active, indexable pages as an XML urlset. The contract is JSON-only, so the XML is returned as a string: store it at the sitemap URL your storefront serves and give it to the webmaster consoles. `collection` narrows the export to one collection.