What to do next on this site

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Build the definitive General cornerstone guide — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Create the single most useful, authoritative page on General anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in General — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest General resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Lock down sensitive data — nothing private is publicly reachable — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in General — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest General resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Add an interactive tool and an email capture for General — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Build one genuinely useful interactive element for General (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in General — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest General resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Publish: A current, data-backed explainer in General — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Trending angle in General. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a General reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Temple etiquette and dress-code guides — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Publish practical traveler guides — what to wear at temples, shoe removal, head-and-feet etiquette, photographing monks respectfully, wai greeting basics — written for visitors, not scholars. Etiquette anxiety is a universal pre-trip search moment, and owning the traveler-facing angle cleanly separates this subdomain from the wholetech reference site. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Publish: The question your General audience is searching most right now — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Trending angle in General. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a General reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Publish: A 'what changed in 2026' round-up for General — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Trending angle in General. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a General reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Cultural itineraries for Lanna and Isaan routes — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Design multi-day cultural routes — Chiang Mai's Lanna temples and crafts, Isaan's Khmer sanctuaries and silk villages — with realistic day sequencing and transport notes. Itinerary content captures travelers at planning stage, and the underserved regional routes differentiate against the Bangkok-Phuket boilerplate saturating this space. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Differentiate and canonicalize against the wholetech twin — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Audit both thaiculture subdomains for overlapping pages; where duplicates exist, keep the traveler version here, canonical or redirect the twin, and split future topics by role — reference there, in-country practice here. Two near-identical subdomains suppress each other; explicit role separation lets both rank for their own intents. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Region-matched Travala placements on itineraries — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Embed Travala affiliate modules (Impact account, live network-wide) matched to each itinerary's actual overnight stops — Chiang Mai stays on the Lanna route, Ubon on the Isaan route. Itinerary readers are actively pricing trips; placement matched to the exact route serves the reader instead of decorating the page. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Deepen the main General guide with current data and examples — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship General page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in General.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Travel-journal art direction with woven borders — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Design as a kept journal: kraft and cream page textures, passport-stamp marks as section badges, ticket-stub dividers, margins bordered with Thai woven-textile patterns in indigo and turmeric tones. Deliberately distinct from the wholetech twin's gold-line reference elegance — this is the notebook in the daypack, not the library volume. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Respectful-packing checklist with Amazon tag — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Publish a packing page keyed to the etiquette guides — temple-appropriate cover-up layers, slip-on shoes for constant removal, modest lightweight clothing, a small daypack — via colinfirthfan-20 links. Tying products to cultural preparation makes this affiliate page genuinely instructive rather than a generic travel-gear dump. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
AdSense on guide and itinerary pages — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Place pub-7759195213529699 units on etiquette guides and itinerary pages between major sections. Pre-trip researchers browse multiple long pages per session, and travel advertisers bid well against Thailand-planning queries; keep density low so the guides retain the calm authority that earns shares in travel forums. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Add a /videos/ page curating the best General videos — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Curate 6–10 authoritative, embeddable videos. Reuses the site's GA + AdSense and deepens the content spine.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful General videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Build /sources/ out to at least 10 authoritative links — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Only 0 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs.

HOW TO APPROACH IT
1. Open the source and confirm it is authoritative and genuinely relevant to General.
2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The link works, is annotated and well-placed, and is a reference a real General expert would trust.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Step-map itinerary visualization — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Render each route as a vertical journey map — numbered stops on a drawn path with travel-mode glyphs (train, songthaew, ferry) between them and day markers as stamp-styled badges. Travelers think in sequences, not paragraphs; the step-map makes routes scannable, screenshotable, and unmistakably this site's format. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Add an FAQ answering the top questions in General — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Pull the real questions people ask in General and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship General page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in General.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
FAQ schema on traveler etiquette questions — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Add FAQPage schema answering 'what should I wear to a Thai temple', 'is it rude to point your feet in Thailand', and 'how do I wai correctly', answered plainly. Maintain both sitemaps, ping IndexNow, and keep af-deploy.py at 90+ so trip-planning AI assistants cite these answers. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Trip-planning email series via newsletter widget — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Embed wholetech.com/newsletter/widget.js offering a short 'Thailand culture prep' series — etiquette, packing, festival timing, regional route ideas — drawing entirely from existing pages. Pre-trip travelers are a naturally time-boxed audience; a sequenced series serves them completely and routes them through the cluster's Travala-bearing itinerary pages. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Add a /live/ news feed for General — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for General: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed General items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Add Article + FAQ structured data — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Verify affiliate links and ad placement resolve correctly — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: thaiculture.wholevoyage.com (live at https://thaiculture.wholevoyage.com/), a General site in the WholeTech network, served from /var/www/thaiculture.wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for thaiculture.wholevoyage.com and no other site — make all changes on thaiculture.wholevoyage.com. Act like a senior editor and web engineer who knows the General niche cold.

GOAL (on thaiculture.wholevoyage.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site thaiculture.wholevoyage.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.