About XKnow: How This Research Is Built

XKnow is a research-backed knowledge system with three outputs: the free guides on this site, an MCP server that lets AI agents search and cite the knowledge base, and the paid vault — 571 interconnected notes covering SEO fundamentals, local search, industry playbooks, SaaS, and knowledge-base engineering. The guides on the site are distilled from that vault, not written as disconnected blog posts.

The site is built to be read by both people and machines: every page has a single clear topic, a canonical URL, structured data, and internal links into the wider library. That is also why the guides are organized by industry and intent rather than by publication date.

XKnow is maintained by the XKNOW RESEARCH team. We publish under an organizational byline rather than individual names on purpose: the work here is a system — a knowledge base, an evidence index, and automated checks — and it is reviewed and revised as a system. When a page cites a source, that source is named on the page, and the reasoning behind the guidance is documented.

This is the same "who, how, and why" transparency Google's people-first content guidance asks for, and it is what the E-E-A-T framework looks for on topics that affect money and well-being ([ev-218]).

Every guide follows the same pipeline:

1. Collect sources first. Claims are gathered from official documentation, industry research, and practitioner write-ups, and each source is recorded with the date it was accessed.
2. Number the evidence. Sources live in a numbered evidence index. When a guide states a figure, that figure traces to a numbered source — the guide's frontmatter lists the evidence it relies on.
3. Check the claims mechanically. A claim map scans every page for numeric statements and flags any that lack a source. The map is public: it is generated from the same files that build this site and served as claim-map.json.
4. Gate the content. Before publishing, pages pass a lint gate covering metadata, structure, internal links, sourcing, and language quality. A failing check blocks the deploy.
5. Verify the built site. After building, an invariant checker confirms canonical URLs, sitemaps, headings, and internal links across every page.

In short: numbers have sources, sources have dates, and the checks run in the open.

Freshness is treated as part of accuracy. Page dates come from the repository history of the page itself, so the "updated" date reflects when the content actually changed. When a platform changes — a deprecated feature, a new requirement, a discontinued result type — the affected pages are revised, and where relevant the change is explained in the guide rather than quietly edited.

Corrections are welcome at hello@xknow.org. If something on a page is wrong, we would rather hear it than keep it. Substantive corrections change the page, and the revision history records it — see our notes on content freshness and how knowledge bases stay current on the XKnow blog.

The free guides answer the questions most people arrive with, and they are written to stand alone. The SEO knowledge hub collects them; SEO 101 is the usual starting point.

The paid SEO Knowledge Base is the layer underneath: 571 cross-linked notes, an index, and an update path, delivered as Markdown and designed to be opened in Obsidian or queried by an AI agent. Buyers receive lifetime updates. Nothing in the paid vault is required to use this site — it exists for readers who want the complete system, sourced and interlinked, instead of assembling it from articles.

Email hello@xknow.org for corrections, sourcing questions, or support with a purchase.