ສິ່ງທີ່​ພະນັກງານ​ຂອງທ່ານ​ຮູ້ ກ່ອນ​ທີ່​ຈະ​ສ້າງ​ສິ່ງ​ໃດ​ສິ່ງ​ໜຶ່ງ

ທຸກໆຄົນສາມາດ​ຊີ້​ໄປ​ຫາ​ແບບ​ທີ່​ມີ​ຢູ່​ໃນ​ເວບໄຊທ໌​ໄດ້. ນີ້ແມ່ນ​ກົດ​ທີ່​ມັນ​ໃຊ້​ກັບ​ທຸກ​ໜ້າ, ເຫດຜົນ​ທີ່​ມີ​ຢູ່​ຂອງ​ແຕ່ລະ​ໜ້າ ແລະ ຂໍ້​ກຳນົດ​ທີ່​ຈະ​ຢຸດ​ການ​ພິມ​ອອກ​ແທນ​ທີ່​ຈະ​ແຈ້ງ​ເຕືອນ​ກ່ຽວກັບ​ມັນ.

ທຸກໆກົດລະບຽບຂ້າງລຸ່ມນີ້ໄດ້ຖືກຈ່າຍໂດຍເຫດການທີ່ເກີດຂຶ້ນໃນເວັບໄຊທີ່ພວກເຮົາປະຕິບັດ - ອັນດັບຫີນ, ການແປທີ່ແຕກ, ຫນ້າທີ່ rendered ໂຄດແຫຼ່ງຂອງຕົນເອງ. ພວກເຮົາບໍ່ໄດ້ຄາດຄະເນໃນການປະຕິບັດທີ່ດີທີ່ສຸດ; ພວກເຮົາໄດ້ຂຽນລົງສິ່ງທີ່ໄດ້ໄປຜິດດັ່ງນັ້ນມັນບໍ່ໄປຜິດໃນເວັບໄຊຂອງທ່ານເຊັ່ນກັນ.

ກົດ​ລະບຽບ​ທີ່​ບັງຄັບ​ໃຫ້​ປິດການ​ອອກ​ຂ່າວ​ຢ່າງ​ເຕັມ​ສ່ວນ: 8 ຂອງ 12. ຫນ້າທີ່ຖືກບລັອກ ຈະຖືກສົ່ງຄືນໄປໃຫ້ພະນັກງານດ້ວຍເຫດຜົນ ແລະ ພະຍາຍາມອີກຄັ້ງ. ມັນຈະບໍ່ເຜີຍແຜ່ ແລະ ແຈ້ງເຕືອນທ່ານຫຼັງຈາກນັ້ນ.

1. One page, one subject

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

2. A description written for a human

ແຈ້ງເຕືອນ

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.

3. No shared body text, ever

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

4. Absolute canonical, paired with hreflang

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

5. Markup may only claim what the page shows

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

6. Django comments are {% comment %}

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

7. Positional {0} slots in translatable strings

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

8. Nothing is indexable until it is finished

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

9. Build the thing, do not describe the thing

ແຈ້ງເຕືອນ

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.

11. Alt text and intrinsic dimensions on every image

ແຈ້ງເຕືອນ

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.

12. Retired URLs return 410, verified

ບັນທຶກ​ການ​ເຜີຍແຜ່

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.

ເຫດຜົນ​ທີ່​ວ່າ​ເປັນ​ຫຍັງ​ສິ່ງ​ນີ້​ເປັນ​ການ​ລິນເຕີ ແລະ​ບໍ່​ແມ່ນ​ຄູ່​ມື​ແບບ

ກົດ​ການ​ທີ່​ມີ​ຢູ່​ໃນ​ຄໍາ​ແນະ​ນໍາ​ແມ່ນ​ຄໍາ​ແນະ​ນໍາ​ - ແບບ​ຢ່າງ​ປະຕິບັດ​ຕາມ​ມັນ​ໃນ​ເວລາ​ຫຼາຍ​ທີ່ສຸດ ແລະ​ບໍ່​ເຮັດ​ໃຫ້​ມັນ​ຢູ່​ຢ່າງ​ສະຫງົບ​ສຸກ​ອີກ​ຕໍ່​ໄປ, ແລະ​ທ່ານ​ຈະ​ພົບ​ເຫັນ​ສາມ​ເດືອນ​ຕໍ່​ມາ​ໃນ​ບົດ​ລາຍ​ງານ​ການ​ຈະລາຈອນ. ດັ່ງນັ້ນ​ພວກ​ນີ້​ຈະ​ແລ່ນ​ເປັນ​ໂປຣ​ແກຣມ, ຫຼັງຈາກ​ທີ່​ຫນ້າ​ໄດ້​ຖືກ​ຂຽນ​ແລະ​ກ່ອນ​ທີ່​ມັນ​ຈະ​ໄປ​ຢູ່​ໃນ​ຊີວິດ​ຈິງ. ຫນ້າ​ທີ່​ລົ້ມ​ເຫຼວ​ໃນ​ການ​ບລັອກ​ກົດ​ການ​ຈະ​ຖືກ​ສົ່ງ​ຄືນ​ກັບ​ເຫດຜົນ​ແລະ​ຂຽນ​ຄືນ​ໃໝ່. ຜົນ​ແມ່ນ​ຢູ່​ໃນ​ການ​ຮັບ​ເອົາ​ທັງ​ສອງ​ທາງ, ສະນັ້ນ​ທ່ານ​ສາມາດ​ເບິ່ງ​ວ່າ​ການ​ກວດ​ສອບ​ທີ່​ໄດ້​ແລ່ນ​ແມ່ນ​ຫຍັງ.

ແລະ​ບໍ່ມີ​ຫຍັງ​ຈະ​ຖືກ​ຈັດ​ອັນດັບ​ຈົນ​ກວ່າ​ທ່ານ​ຈະ​ເວົ້າ​ວ່າ

ທຸກ​ເວບ​ໄຊ​ທ໌​ຈະ​ເລີ່ມ​ຕົ້ນ​ດ້ວຍ noindex. ບໍ່ແມ່ນ​ເປັນ​ການ​ຕັ້ງ​ຄ່າ​ແບບ​ເດີມ​ທີ່​ທ່ານ​ຕ້ອງ​ຄົ້ນ​ພົບ - ຕາມ​ກົດ​ລະບຽບ​ທີ່​ linter ປະຕິບັດ, ຍ້ອນ​ວ່າ​ເວບ​ໄຊ​ທ໌​ເຫຼົ່ານີ້​ແບ່ງປັນ​ໂດເມນ​ແລະ​ເພື່ອນ​ບ້ານ​ທີ່​ບໍ່​ດີ​ຄົນ​ໜຶ່ງ​ກໍ່​ເຮັດ​ໃຫ້​ທຸກ​ຄົນ​ເຈັບ​ປວດ​ຢູ່​ທີ່​ນັ້ນ. ເມື່ອ​ເວບ​ໄຊ​ທ໌​ຂອງທ່ານ​ມີ​ຄ່າ​ທີ່​ຈະ​ຄົ້ນ​ພົບ, ທ່ານ​ເປີດ​ການ​ສ້າງ​ລາຍ​ການ​ໃນ​ການ​ຕັ້ງ​ຄ່າ ແລະ​ມັນ​ຈະ​ເລີ່ມ​ການ​ຄຣາວ​ມັນ​ເອງ.

ແລ່ນ​ການ​ປ່ຽນ​ຄັ້ງ​ທຳ​ອິດ​ຂອງທ່ານ​ຟຣີ