任何人都可以在网站上点出模型。 这是它适用于每页的规则, 每个页面存在的原因, 以及其中哪个停止出版而不是警告。
下面的每一个规则都是由我们所运行的网站上的事故所支付的——一个排名悬崖,一个破碎的翻译,一个提供了自己源代码的页面。我们没有猜测最佳做法;我们正在记录已经发生的错误,因此在你的网站上也不会出错。
阻止公布彻底的条例: 8 出月 联 和 12. 封锁页面被带回给员工, 并再次尝试。 之后不会公布或警告您。
Exactly one <h1>. A descriptive <title> of 15-60 characters.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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}.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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.
为什么: 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.
只有在指令中生活的规则是建议——模型大部分时间都遵循它,静悄悄地遵循它,其余的不做,三个月后在交通举报中发现。因此,这些规则在页面写好之后和启用前以代码形式运行。一个没有执行阻塞规则的页面被以理由交还,并重写。结果在接收方式上,这样你就能看到哪个检查运行。
每个网站都开始没有索引。 通常情况下, 您不必发现 Linter 强制执行者, 因为这些网站共享一个域, 一个坏邻居伤害了所有网站。 当网站值得查找时, 您可以在设置中打开索引, 开始爬行 。