Wat jou werknemer weet voordat dit enigiets opbou

Exactly one <h1>. A descriptive <title> of 15-60 characters.

Waarom: Title is the strongest per-page signal Google has. Google rewrites titles for the SERP most of the time, but the signal it forms from yours still affects ranking, and a generic or duplicated title reads as a quality problem.

A meta description of 140-158 characters, unique to the page.

Waarom: Description does not rank the page, it decides whether anyone clicks it. Too short wastes the snippet; too long truncates mid-sentence.

Every page gets body copy and FAQ answers written for that page. Never a shared template with a noun swapped in.

Waarom: This is the one that costs months. A site we run shipped ~1700 pages on one generic FAQ body and a site-level quality classifier suppressed the whole domain — pages still indexed, ranking gone, no manual action to appeal. Recovery ran on core-update timescale.

Every page self-canonicalises with an absolute URL. Any hreflang cluster ships alongside that canonical, also absolute.

Waarom: Relative hrefs are silently dropped. hreflang without a self-canonical fills the index report with "Duplicate without user-selected canonical" — 56,801 pages on one site we run.

Structured data mirrors the visible text exactly. Schema goes on the page types that earn a rich result, not on everything.

Waarom: Schema is not a general ranking input and not required for AI search -- Google says so directly. Markup that claims a price or a question the page never shows is a violation that can earn a manual action.

Never {# #}. Not even on one line.

Waarom: Django's template lexer regex has no DOTALL flag, so {# #} only closes on its own line. A multi-line one renders as visible page text, and if it contains a {% %} substring the lexer treats it as a real tag and every render crashes. Both have happened in production.

Any string that will be machine-translated uses {0}, {1} — never {name}.

Waarom: MT engines translate or transliterate the word inside the braces, or drop a brace entirely. A numeric slot has no word to translate and survives intact. This silently broke about 10% of non-English rows on one site before anyone noticed.

Pages ship noindex. Indexing is a deliberate opt-in by the owner, per site.

Waarom: These sites share a wildcard domain. One spam tenant indexed on that wildcard damages every other tenant on it, and a half-finished page indexed on day one takes months to undo.

A page either does something useful or says something specific. A page that only describes a tool is not a page.

Waarom: Thin wrappers around someone else's API are the clearest signal a quality classifier has. Real utility is what survives a core update.

Every indexable page has at least one inbound internal link.

Waarom: Internal links pass ranking signal and drive crawl. A page reachable only from the sitemap gets crawled a few times and then largely forgotten.

Every <img> has alt text and explicit width/height.

Waarom: Alt text is an accessibility requirement first and an indexing signal second. Missing dimensions cause layout shift, which is a Core Web Vitals failure on mobile — and mobile is what gets indexed.

A removed page returns 410 Gone, confirmed by an actual request after deploy.

Waarom: A 404 lingers as a soft-404 for months; a 410 deindexes cleanly. And per-view dispatch often intercepts the request before the 410-returning view is ever reached, so the check has to be a real HTTP request, not a code read.