Skip to main content
TheDocs
Sign in Book a Demo
Feature

Found by search engines. Quoted correctly by AI.

Two audiences now read your documentation before your customers do. Both need the same thing: clean structure, honest metadata, and a machine-readable map.

Start free trial Book a demo
  • Structured data generated
  • llms.txt included
  • MCP endpoint

How does TheDocs handle documentation SEO?

Every published article gets a clean, readable URL, an editable title and meta description, canonical tags, Open Graph and Twitter cards, and schema.org structured data generated from the article's own content. The portal produces an XML sitemap and correct hreflang across languages. For AI systems, TheDocs also publishes an llms.txt index and, on Business and above, an MCP endpoint that assistants can query directly.

  • Readable URLs with redirects preserved from your previous site.
  • Per-article title, meta description, canonical and noindex control.
  • TechArticle, FAQPage, HowTo and BreadcrumbList structured data.
  • XML sitemap, robots.txt and hreflang generated and kept current.
  • llms.txt index and an MCP endpoint for AI assistants.
  • Core Web Vitals monitored per portal and reported.
In detail

Optimising for two very different readers

Search engines

Documentation is unusually good SEO material: it answers specific questions in specific words. Most of it underperforms only because the technical layer is missing.

  • URLs derived from the article title, editable, and with an automatic redirect whenever one changes.
  • Title and meta description editable per article, with a live preview of the search result and a length warning.
  • Structured data generated from the content - a step-based procedure emits HowTo, a Q&A section emits FAQPage.
  • Canonicals across versions and languages, so v2 and v3 of the same article never compete.
  • Drafts, archived versions and private projects are noindexed automatically.
  • Fast pages by default, with Core Web Vitals reported per portal.

The importer generates a redirect map from your old URLs, so a migration does not cost you the rankings you already have.

AI assistants

An increasing share of product questions are now answered by an assistant that read your documentation second-hand. You want it reading the current version.

  • llms.txt: a plain-text map of your documentation with a description of each section, generated from your live structure.
  • llms-full.txt: extended context including what your product does and does not do, so an assistant is less likely to guess.
  • MCP endpoint: assistants query your published documentation live instead of relying on a crawl that may be months old.
  • Clean semantic HTML with real headings, so extraction produces the passage rather than the navigation.
  • Answer-first article structure encouraged by the templates, because that is what gets quoted.
Per-article

Controls you get per article

URL slug

Edited freely, with the previous URL kept as a 301 redirect automatically.

Title and description

Separate from the on-page H1, with a search preview and length guidance.

Index control

Noindex a single article or a whole category without unpublishing it.

Social card

Per-article Open Graph image, or an automatic one generated from the title.

Schema type

Override the detected structured data type when the automatic choice is wrong.

Redirects

Manage redirects in bulk, import them as CSV, and see which ones are being hit.

Related features

Knowledge Base Portal

A branded, searchable self-service site your customers actually read.

Multi-Language Docs

One article, many languages, with translation status tracked per version.

Content Analytics

See what readers search for and never find, then fix the gap.

Import & Migration

Move in from Word, PDF, Confluence, Notion, GitBook or Zendesk Guide.

Site Customisation

Your domain, your brand, your layout - without touching code.

AI Search

Natural-language answers that cite the exact article they came from.
Frequently asked

Questions people ask before they start

Because most people looking for your help centre do not start on your help centre. They search the error message. An article that ranks catches that person before they open a ticket, and it also catches prospects evaluating your product.

TechArticle or Article markup on every page, FAQPage where an article has a question and answer section, HowTo for step-based procedures, BreadcrumbList for navigation, and Organization and WebSite on the portal. All of it is generated from the article itself, so it cannot drift.

It is a plain-text index of a site written for language models rather than browsers. It gives an AI assistant a reliable map of your documentation, which makes it far more likely to answer about your product from your own current content rather than a stale crawl.

Yes. Per-article noindex, per-category rules, and automatic noindex on drafts and older product versions so they never compete with your current documentation in search results.

A subdirectory of your main domain usually consolidates authority better. TheDocs supports both - help.yourcompany.com, or yourcompany.com/docs behind your own proxy.

Let your documentation catch the people searching for the error message.

Start free for 14 days. No credit card, no setup fee, and your content is yours to export at any time.

Start free trial Book a 30-minute demo

Questions first? Email sales@thedocs.in or call +91 8585953085.