v2.14.1 docs header polish: the docs-center search trigger is now a prominent search field right next to the brand — placeholder text, ⌘K hint, icon-only on narrow screens.
AnvilWiki
Esc Close · ↵ Search
Powered by Pagefind
中文

Learning Manual

Zero experience required: pick the right game, install the tools, launch your site, write 10 pages with AI on day one, get on Google, turn on ads, run a 30-minute weekly ops loop — then turn your first site into a template, batch-create dozens of traffic-entrance pages, and climb from indexed to ranking and AI-cited.

32 lessons

  1. Know the Business
  2. 1 How This Business Makes Money: From Traffic to Payout Understand the money chain: players search, Google ranks you, ads get seen, advertisers pay. Three minutes to set honest expectations for month one.
  3. 2 The Full Map: Six Stops to Your First Site The six-stop subway map: pick and validate, stand it up, content, launch and index, monetize, operate — each with lessons, time cost, and what you carry away.
  4. Pick & Validate
  5. 3 Where to Find Candidates: 20 Minutes a Day, 10 Candidates Three starter channels, 20 minutes daily, steadily 3-5 new game candidates into a candidate table. A thin pool makes every later gate useless.
  6. 4 Reading Google Trends: Five Minutes to Confirm Real Search Validate each candidate in Google Trends compare mode against a baseline query: read level, slope, and cycle. Two-source rule: two unrelated places minimum.
  7. 5 Reading the Results Page: Two Minutes to See How Crowded Read page one of the results for two queries: under 10 results or PDFs and forums = open seats; a thin stale Fandom = beatable; thick daily pro sites = drop.
  8. 6 Search Intent: Answer the Question Right and You Win A full page one can still hold open seats — its results may answer the wrong question. One worked example, row by row, plus a five-step intent checklist.
  9. 7 Score and Decide: Two Tables, Two Days, One Decision Funnel every signal into a scorecard (four items, 60 to pass) and a decision ledger, then commit build-or-drop within two days. Full AI prompt included.
  10. 8 The Day-One 10-Page List: Turning a Decision into a Writing Plan Turn the verdict into a 10-row writing plan — codes page first, then guides, tier list, FAQ, and your validated window queries. Stage one's graduation output.
  11. Stand It Up
  12. 9 Install the 6 Tools: Set Up Once, Never Again Terminal, GitHub account (with 2FA), Node, pnpm, Git, AI assistant — each with what you'll see and a check. Installed once, used every lesson, 30 minutes total.
  13. 10 Run Your Site: See It Working in Three Steps Fork the template into your account, clone it to your computer, and pnpm dev opens the sample site at localhost:4321 — three steps, each with what you'll see.
  14. 11 Make It Yours: One Command, One Q&A pnpm apply-template asks one question at a time and rewrites every config. Full 15-question answer table, a 2-minute favicon swap, and the acceptance checklist.
  15. 12 Theme & Homepage: The Recolor Rule and Homepage Copy Recoloring means all 8 variable lines atop globals.css move together — 4 leaves the old hue. Homepage copy edits only the JSON home section. Optional lesson.
  16. Content Engine
  17. 13 Your First Guide: One Hour of Play, One QA-Passing Page Open the site folder in your AI assistant, play an hour, take 20 notes, paste the guide prompt. Frontmatter, the QA gate, and draft — plus the intent table.
  18. 14 The Codes Page: Biggest Traffic, Biggest Risk The highest-traffic page is also the most fragile: codes come only from lists you saw yourself. Full prompt, video red lines, and the draft-to-live flow.
  19. 15 Tier Lists & Media: Tables for Verdicts, Images for Proof Tier lists put your judgment into a table with version stamps; media comes via three legal channels — own captures, official kits, CC stock. Two prompts.
  20. 16 The QA Pipeline: Finish One, Verify One Three gates per page: AI QA green, eyeball the page, answer the TBD list; no data means draft. One commit per page. Never batch-verify — errors copy.
  21. 17 The Launch Batch: 10 to 15 Pages, Shipped in Waves Launch 10-15 core pages first — codes, tier, guide queries first — then 10+ weekly with drafts flipped one by one. Stage three graduates here.
  22. Launch & Get Indexed
  23. 18 Take Your Site Live: Onto the Free Shelf Push the site to GitHub, connect Cloudflare's free shelf for a global URL, handle the beginner trap (which settings win), and buy-and-bind a domain. All free.
  24. 19 Get Google to Know You: Three Indexing Tasks Register Google Search Console (GSC), submit the sitemap, and request indexing for key pages — 20 minutes on launch day, and Google starts shelving your pages.
  25. 20 Install the Two Counters: Who Came, What They Did Launch-day counters: Cloudflare Web Analytics (a token) and the Clarity heatmap (a script) — ten minutes to learn who came, from where, and where they get stuck.
  26. 21 First-Week Numbers: One Number per Panel One fixed weekly reading: GSC for click queries, Cloudflare for traffic, Clarity for stuck points — against four pass lines. Conclusions must cite panel numbers.
  27. Monetize & Operate
  28. 22 Turn On Ads: Timing and Setup Rank first, ads second. Self-check, audit, apply to AdSense, fill four Cloudflare variables — empty vars render nothing, and revenue is 100% yours.
  29. 23 The Three Payout Tasks: W-8BEN, PIN, Wire Start on approval day: W-8BEN for the 10% treaty rate, the PIN postcard (4 attempts, 4-month limit), wire with pinyin payee and SWIFT. Don't race the payout window.
  30. 24 Add GA4: Understand How They Left Optional upgrade: when questions move from 'how many' to 'which path', GA4 goes in — property, Measurement ID into PUBLIC_GA_ID, realtime-report verify.
  31. 25 Thirty Minutes Weekly: The Freshness Loop Monday, 30 minutes: refresh-audit turns stale pages into todos, codes get updated, GSC picks next topics. Monthly upstream sync; quarterly SEO checkup.
  32. 26 Clone Your Site: The 30-Minute Standard Flow Clear template-audit to zero, save a rebrand checklist, then four steps per clone: duplicate, apply-template, content, build. wrangler.toml is the trap.
  33. 27 Batch-Create Inner Pages: Dozens of Traffic Entrances Homepages win little search — dozens of inner pages, each aimed at one query, are the workhorse. Three steps: list queries, one prompt, bulk scaffolding.
  34. 28 Rank One Keyword: From Indexed to Searched One page, one query: judge which queries are worth it, then fill every slot on the page — title, question H2, direct-answer summary, tables, cover. Two AI prompts.
  35. 29 Slow Variables: Trust & Backlinks The compounding quarter of rankings: freshness, bylines, internal links; anti-spam red lines; backlink timing and the 2026 expired list. The manual closes here.
  36. Appendices
  37. 30 Appendix A · The Red-Line Master List Every red line from the manual on one page — content, AdSense, backlinks, copyright, engineering — a 60-second scan before anything ships.
  38. 31 Appendix B · The Troubleshooting Tree Six frequent symptoms with answers: not indexed, 404, red build, blank ad slots, no analytics, flat rankings — one path each, pointing at the lesson and command.
  39. 32 Appendix C · Glossary & Command Cheat Sheet Every word card in one place — 30+ terms by theme — plus twenty pnpm commands grouped by scenario: writing, QA, config, ops, assets.