SEO and GEO maintenance
This document defines the ongoing SEO and GEO (Generative Engine Optimization) maintenance process for docs.novu.co.Monthly Google Search Console review
- Open Google Search Console for
docs.novu.co. - Review Queries for the notification infrastructure keyword cluster:
- notification infrastructure
- in-app notification component
- notification API
- Novu inbox
- transactional notifications
- Prioritize pages with high impressions but low CTR (rewrite title/description).
- Prioritize pages with low average position on target queries (expand content depth, add internal links).
- Submit or verify
https://docs.novu.co/sitemap.xmlin the Sitemaps report.
Pre-deploy checklist
Before merging documentation changes:- Every new MDX page has unique
titleanddescriptionfrontmatter - API endpoint pages include a
descriptionand 1–2 sentence intro before the OpenAPI block - Provider pages use the
{Provider} {Channel} Integration with Novutitle pattern - Headings on key pages use question format where appropriate
- Images include descriptive alt text
- Run
mint broken-linksfrom thedocs/directory (requires Mintlify CLI) - Run
mint scoreto validate SEO/GEO signals includingrobotsTxtAllowsAI
Quarterly AI citation testing
Test these questions in ChatGPT, Perplexity, and Claude:- How do I authenticate API requests with Novu?
- What are Novu API rate limits?
- How do I add in-app notifications to a Next.js app?
- What is Novu and what channels does it support?
- How do Novu workflows work?
- How do I send a transactional notification with Novu?
- What is Novu Inbox?
- How do I migrate from Knock to Novu?
- Can I self-host Novu?
- What is Agent Communication Infrastructure (ACI)?
- Whether docs.novu.co is cited
- Whether cited content is accurate
- Whether code examples match current API patterns
Technical references
llms.txt:https://docs.novu.co/llms.txt(Mintlify auto-generated)sitemap.xml:https://docs.novu.co/sitemap.xmlrobots.txt:https://docs.novu.co/robots.txt- Mintlify SEO config:
docs.json→seoblock