文章更新進度

1. Before you start — setup & ground rules

1.1 Cadence

Publish in waves of ~6–8 articles, one wave every 1–2 weeks — the rhythm of your last two real waves (10 on 2026-05-14, 16 on 2026-06-25). Each “article” is a bilingual pair (one EN post + one TC post), so a wave of 8 is 16 posts. All 19 waves then spread over roughly 6–9 months.

1.2 Each file already contains its title, slug and meta

You never invent SEO settings. Every .html file opens with a comment block that states them:

<!-- WordPress SEO: Set post title to: ...
     Set slug to: ...
     Set meta description to: ... -->

TC files carry the same in Chinese (文章標題 / 網址別名 / 文章摘要). Read that block first for every file — it is the source of truth. The slugs printed in Section 4 below are the EN slugs; trust the file if it ever differs.

1.3 Tools

• Block editor “Code editor” (top-right ⋮ → Code editor) or Classic editor Text tab — the bodies are clean HTML meant for code mode, not visual.
• SEO plugin (Yoast / Rank Math) for meta description + focus keyphrase.
• Multilingual plugin (WPML / Polylang): EN posts → English (under /en/…), TC posts → Chinese, linked as translations.

2. The repeatable recipe — publishing ONE bilingual article

The loop you’ll run 134 times. Do the EN post and the TC post as a pair, then link them.

1. Open the EN file; read its top comment block (Title, Slug, Meta).
2. Copy the body only — everything below the comment blocks (first <p>/<h2> onward).
3. WordPress → Posts → Add New.
4. Switch to Code editor, paste the body, switch back to visual to check.
5. Set Title from the comment block.
6. Set the slug from the comment block; confirm EN resolves under /en/….
7. SEO fields: paste meta description; set focus keyphrase to the target keyword.
8. Language = English; set category, featured image, tags.
9. Preview: headings, any table/FAQ, internal links, and CTA = “Giga Accounting by 凌峰會計” + the canonical 10GB / no-need-to-purge line.
10. Publish; record the live URL.
11. Repeat for the TC file (Language = Chinese; paste the Chinese slug exactly).
12. Link the two as translations.

3. Live-site changes & corrections (all in one place)

These are edits to pages that are already published. Most jobs are small and can be done now; the G-SYS 301s (3.3) are tied to Wave 14, and the H-series overwrites (3.6) replace eight live posts with their re-written versions. (Jobs 3.5 and 3.6 added 2026-07-02.)

3.1 OD-A — the 系統 keyword tuning (5 live pages)

Why: your TC corpus targets 會計軟件 (software). The terms 會計系統 and 雲端會計系統 are owned by no page. S1 (a new article) grabs 會計系統; these edits make the existing R2 page also rank for 雲端會計系統 on its current authority.

Page 1 — R2-TC (cloud guide, /香港中小企雲端會計-2026年完整指南) · do NOT change slug

1a · Change the title / H1 to:

香港中小企雲端會計系統完整指南（2026）

1b · Replace the meta description with:

一文睇清香港中小企雲端會計系統：雲端會計系統有咩好處、點揀、同本地部署有咩分別，以及 2026 年揀選雲端會計系統的香港實務考量。

1c · Add this sentence near the top of the opening paragraph:

對好多香港中小企嚟講，由單機軟件轉用<strong>雲端會計系統</strong>，往往係帳目由「報稅先做」變成「日日睇得到」的轉捩點。

1d · Paste this as a NEW H2 section, mid-article (after the benefits section):

<h2>揀選雲端會計系統的 6 個香港考量</h2>
<p>市面上的<strong>雲端會計系統</strong>功能相近，但適唔適合香港中小企，要睇本地實務：</p>
<ul>
<li><strong>HKFRS 格式報表</strong>——核數師收貨的輸出，而唔係淨係一個盈利數字。</li>
<li><strong>雙語單據同介面</strong>——中英文發票同報表。</li>
<li><strong>香港合規鈎子</strong>——強積金、IR56、兩級制利得稅、商業登記提醒。</li>
<li><strong>一個授權多公司</strong>——而唔係每間公司分開收費。</li>
<li><strong>本地支援同數據駐留</strong>——明白香港核數、同你同一時區。</li>
<li><strong>匯出權利</strong>——確認隨時攞得返自己盤數。</li>
</ul>
<p>想由更高層次了解「系統 vs 軟件」的分別，可參考我哋的<a href="REPLACE-WITH-S1-LIVE-URL">會計系統選擇指南</a>。</p>

1e · Add ONE in-body link on the phrase 雲端會計系統 → the service page:

…一套香港本地化的 <a href="https://linfungaccounting.com/%e9%9b%b2%e7%ab%af%e6%9c%83%e8%a8%88%e7%b3%bb%e7%b5%b1">雲端會計系統</a>…

(That %e9%9b%b2… URL is the encoded form of /雲端會計系統; it’s already live, no S1 dependency.)

Page 2 — the /雲端會計系統 service page

• Ensure the H1 / page title literally contains 雲端會計系統 (not just 雲端會計).
• Add one link to R2-TC, anchor 雲端會計系統指南.
• After S1 publishes, add one link to S1, anchor 會計系統.

Pages 3 & 4 — R1-TC and R8-TC (one sentence each)

R1-TC (會計軟件 buyer’s guide) — add after the intro:

留意「<strong>會計軟件</strong>」同「<strong>會計系統</strong>」唔同：前者係單一程式，後者係多模組整合。想分清楚，可睇<a href="REPLACE-WITH-S1-LIVE-URL">會計系統選擇指南</a>。

R8-TC (會計軟件功能介紹) — add one line:

當你需要的唔止係軟件功能，而係一套整合的<a href="REPLACE-WITH-S1-LIVE-URL">會計系統</a>時，評估重點會由「功能」轉向「整合同導入」。

Page 5 — D10 (API/integrations, already live)

Add one internal link: phrase 會計系統 as anchor → your S1 pillar.

3.2 A14 — fix one dead link on the live post

A14 (Desktop vs Cloud Accounting Software) is already live. It contains a link to an old competitor post that was scrapped, so that link now 404s. Open the live A14 post and either remove the link or retarget it to a related live post (e.g. R2 cloud guide). One-minute WordPress edit.

3.3 G1 slug + the G-SYS 301 redirects (do at Wave 14)

3.4 Verify the June 2026 TC wave — ✅ DONE 2026-07-02

3.5 301-redirect the dead /香港公司最常用的會計軟件 URL (✅ done 2026-07-09)

How to set it, easiest route first:

• If you have Rank Math or Yoast Premium: WordPress admin → Rank Math → Redirections (or Yoast → Redirects) → Add New → paste source + target → set type 301 → Save.
• If not: install the free “Redirection” plugin (by John Godley) → Tools → Redirection → Add New → source + target → Save. (Leave the type as the default 301.)

Before you save: paste the target URL into a browser to confirm it loads (no trailing-slash/encoding surprise). After you save: visit the old dead URL once — it should now land on the best-software page instead of the 404. Then submit the old URL in Google Search Console (URL Inspection → Request Indexing) to speed up the hand-over.

# nginx: server-level fallback (put in the server { } block, then: nginx -t && systemctl reload nginx).
# nginx decodes %XX (any case) before matching, so the readable source below also catches Google's uppercase-encoded URL.
location = /香港公司最常用的會計軟件 { return 301 https://linfungaccounting.com/%e9%a6%99%e6%b8%af%e6%9c%80%e4%bd%b3%e6%9c%83%e8%a8%88%e8%bb%9f%e4%bb%b6%ef%bc%882026%e5%b9%b4%e4%b8%ad%e5%b0%8f%e4%bc%81%e6%8c%87%e5%8d%97%ef%bc%89; }

3.5b — Four more dead-URL 301s: cloud (雲端會計) orphans (do now · added 2026-07-09)

Alternative target (if you’d rather funnel to the product page than the guide): TC → the /雲端會計系統 service page; EN → the /en/cloud-accounting service page. Either is fine — R2 keeps equity flowing content-to-content, the service page funnels to the product.

How to set them: same as 3.5 — Redirection plugin (or Rank Math / Yoast) → Add New → paste source + target → type 301 → Save, once per row. The www.→non-www redirect already works, so a path-only source match catches them. After saving, load each old URL once to confirm it lands on R2, then submit it in Search Console (URL Inspection → Request Indexing).

# nginx: server-level fallback (put in the server { } block, then: nginx -t && systemctl reload nginx).
# nginx decodes %XX (any case) before matching, so the readable Chinese sources below also catch Google's uppercase-encoded URLs.
location = /香港雲端會計軟件推薦 { return 301 https://linfungaccounting.com/%e9%a6%99%e6%b8%af%e4%b8%ad%e5%b0%8f%e4%bc%81%e9%9b%b2%e7%ab%af%e6%9c%83%e8%a8%88-2026%e5%b9%b4%e5%ae%8c%e6%95%b4%e6%8c%87%e5%8d%97; }
location = /適合香港企業的雲端會計 { return 301 https://linfungaccounting.com/%e9%a6%99%e6%b8%af%e4%b8%ad%e5%b0%8f%e4%bc%81%e9%9b%b2%e7%ab%af%e6%9c%83%e8%a8%88-2026%e5%b9%b4%e5%ae%8c%e6%95%b4%e6%8c%87%e5%8d%97; }
location = /cloud-accounting-software-blog-post { return 301 https://linfungaccounting.com/en/cloud-accounting-for-hong-kong-smes-a-complete-guide-2026; }
location = /en/cloud-accounting-software-2 { return 301 https://linfungaccounting.com/en/cloud-accounting-for-hong-kong-smes-a-complete-guide-2026; }

3.6 H-series — overwrite 8 live posts with their re-writes (content ready 2026-07-02)

The H-series (see H-series-article-plan.md) is 8 full re-writes of live articles, each rebuilt to the competitor-winning formula (comparison table + FAQ + FAQPage JSON-LD + 軟件/系統/雲端 pairing + licensed-firm framing). Each overwrites its named original in place; files are in articles-not-yet-published/, EN + TC.

Per post: open the live post → replace the body with the H file’s content (everything below the comment blocks) → update the SEO title + meta per the H file’s header comment → keep the slug unchanged → paste the FAQ <script type="application/ld+json"> block into a Custom-HTML block (or, if your theme strips inline scripts, use your SEO plugin’s FAQ block with the same Q&A) → confirm the comparison table renders → Update → request re-indexing in Search Console.

4. The full 134-article roadmap — 19 waves

Grouped into five phases. Slugs shown are the EN slugs; the TC equivalents are in each file’s header. Keep ~1–2 weeks between waves and the running software/services mix near 60/40.

On each ⚙ article, link 會計系統 → the S1 pillar.

5. After every wave — three closing steps

1. Capture the live slugs. WordPress can auto-adjust a slug on publish. Record each article’s actual live URL and fix any internal cross-link that pointed at a different slug. (Most relevant for the G25–G40 group, whose cross-links may use slugs that differ from the live ones.)
2. Move the files. Relocate the wave’s .html files from articles-not-yet-published\ to articles-already-published\. (Helper: move-published-wave.bat.)
3. Update CLAUDE.md. Refresh the Status block counts, the live-posts list, and the “Last live-site scan” date. Close any editor / pause sync first.

6. Final QC checklist (every post, before Publish)

• Title, slug and meta description match the file’s comment block exactly.
• TC slug contains the intended Chinese keyword (never an auto-generated string).
• Focus keyphrase set to the article’s target keyword.
• EN post = English; TC post = Chinese; the two linked as translations.
• Headings render; any comparison table or FAQ block displays correctly.
• Internal links resolve (or are logged for a quick post-publish WP fix).
• CTA reads “Giga Accounting by 凌峰會計” + the canonical 10GB / no-need-to-purge line — never “Lin Fung” or “聯豐”.
• ⚙ articles link 會計系統 / ERP 系統 to the S1 pillar.
• Review/competitor articles (E10–E13, F13–F18, G6, G20–G24, G44, G33): pricing, editions and claims re-verified as current.
• G1 only: slug = accounting-system-hong-kong-comparison (not the filename slug); 301 redirects in place.
• Live URL recorded; file moved to articles-already-published\; CLAUDE.md updated.

Sequence: live-site OD-A edits (§3.1) alongside Wave 1 → Waves 1–8 clear the A–E backlog (系統 foundation first) → Waves 9–13 the F-series → Waves 14–19 the G-series (after the §3.3 G1-slug + 301 work). 19 waves, ~6–8 articles each, ~1–2 weeks apart; ship-then-fix-in-WordPress throughout; slugs captured and CLAUDE.md updated after every wave.