A prioritized, living to-do list for wholevoyage.com, built from this site's sources and current trends in Hospitality. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Security | 2026-06-19 | on wholevoyage.com Lock down sensitive data — nothing private is publicly reachable |
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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Lock down sensitive data — nothing private is publicly reachable — on the site 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. | ||||
| 2 | 99 | Security | 2026-06-19 | on wholevoyage.com Make the site mythos-attack-proof — harden against automated & AI-agent abuse |
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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site 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. | ||||
| 3 | 98 | Security | 2026-06-20 | on wholevoyage.com Verify HTTPS, security headers & a safe Agents-First surface |
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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site 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. | ||||
| 4 | 95 | Flagship | 2026-06-22 | on wholevoyage.com Build the definitive Hospitality cornerstone guide |
Create the single most useful, authoritative page on Hospitality 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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Build the definitive Hospitality cornerstone guide — on the site wholevoyage.com. WHY IT MATTERS Create the single most useful, authoritative page on Hospitality 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 Hospitality — 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 Hospitality 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. | ||||
| 5 | 95 | Flagship | 2026-06-22 | on wholevoyage.com Add an interactive tool and an email capture for Hospitality |
Build one genuinely useful interactive element for Hospitality (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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Add an interactive tool and an email capture for Hospitality — on the site wholevoyage.com. WHY IT MATTERS Build one genuinely useful interactive element for Hospitality (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 Hospitality — 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 Hospitality 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. | ||||
| 6 | 92 | Flagship | 2026-06-24 | on wholevoyage.com Make the homepage genuinely distinctive — kill any generic-template feel |
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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site 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 Hospitality — 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 Hospitality 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. | ||||
| 7 | 88 | Popularity | 2026-06-27 | on wholevoyage.com Destination guides anchored to real network properties |
Write destination guides only where the network has real depth: Koh Samui and Thai villa regions from thaivillaexchange, plus cruise regions from the HulloShips atlas pages. Interlink hub-to-property both directions so wholevoyage becomes the topical umbrella that lifts every hospitality property's search standing simultaneously. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Destination guides anchored to real network properties — on the site wholevoyage.com. WHY IT MATTERS Write destination guides only where the network has real depth: Koh Samui and Thai villa regions from thaivillaexchange, plus cruise regions from the HulloShips atlas pages. Interlink hub-to-property both directions so wholevoyage becomes the topical umbrella that lifts every hospitality property's search standing simultaneously. (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. | ||||
| 8 | 87 | Trends | 2026-06-28 | on wholevoyage.com Publish: A current, data-backed explainer in Hospitality |
Trending angle in Hospitality. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Publish: A current, data-backed explainer in Hospitality — on the site wholevoyage.com. WHY IT MATTERS Trending angle in Hospitality. 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 Hospitality 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. | ||||
| 9 | 86 | Trends | 2026-06-28 | on wholevoyage.com Publish: The question your Hospitality audience is searching most right now |
Trending angle in Hospitality. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Publish: The question your Hospitality audience is searching most right now — on the site wholevoyage.com. WHY IT MATTERS Trending angle in Hospitality. 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 Hospitality 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. | ||||
| 10 | 85 | Popularity | 2026-06-29 | on wholevoyage.com Own the book-direct-versus-OTA editorial angle |
Publish a definitive, numbers-honest series on why booking owner-direct beats OTAs: commission math, cancellation flexibility, who actually answers the phone. Link the network's real proof points, Sandalwood's SiteMinder book-direct, thaivillaexchange, and the HulloShips vessel exchange. A genuine point of view earns links generic travel content never will. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Own the book-direct-versus-OTA editorial angle — on the site wholevoyage.com. WHY IT MATTERS Publish a definitive, numbers-honest series on why booking owner-direct beats OTAs: commission math, cancellation flexibility, who actually answers the phone. Link the network's real proof points, Sandalwood's SiteMinder book-direct, thaivillaexchange, and the HulloShips vessel exchange. A genuine point of view earns links generic travel content never will. (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. | ||||
| 11 | 81 | Popularity | 2026-07-02 | on wholevoyage.com Villa and vessel walkthrough /videos/ page |
Build a /videos/ page of villa tours, ship walkthroughs, and destination footage, every embed verified with check-embed.mjs and non-embeddable entries dropped and renumbered. Walkthrough video is the highest-intent content format in hospitality; travelers watch far longer than they read, and dwell time feeds everything else. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Villa and vessel walkthrough /videos/ page — on the site wholevoyage.com. WHY IT MATTERS Build a /videos/ page of villa tours, ship walkthroughs, and destination footage, every embed verified with check-embed.mjs and non-embeddable entries dropped and renumbered. Walkthrough video is the highest-intent content format in hospitality; travelers watch far longer than they read, and dwell time feeds everything else. (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. | ||||
| 12 | 79 | Trends | 2026-07-03 | on wholevoyage.com Publish: A 'what changed in 2026' round-up for Hospitality |
Trending angle in Hospitality. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Publish: A 'what changed in 2026' round-up for Hospitality — on the site wholevoyage.com. WHY IT MATTERS Trending angle in Hospitality. 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 Hospitality 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. | ||||
| 13 | 77 | Revenue | 2026-07-05 | on wholevoyage.com Travala links where no book-direct partner exists |
For destinations outside the network's owner-direct partners, add Travala affiliate booking links via the live Impact account. Keep the standing rule intact: villa and partner-property pages stay book-direct with zero OTA links, so the editorial position and the monetization never contradict each other on the same page. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Travala links where no book-direct partner exists — on the site wholevoyage.com. WHY IT MATTERS For destinations outside the network's owner-direct partners, add Travala affiliate booking links via the live Impact account. Keep the standing rule intact: villa and partner-property pages stay book-direct with zero OTA links, so the editorial position and the monetization never contradict each other on the same 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. | ||||
| 14 | 76 | Revenue | 2026-07-05 | on wholevoyage.com Voyage-deals newsletter via the widget |
Embed https://wholetech.com/newsletter/widget.js offering a monthly owner-direct deals digest: new villas, vessel listings, seasonal windows worth booking. An owned list converts repeat bookings without platform fees, and it is the natural upsell channel for partner featured placements once subscriber counts are honestly reportable. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Voyage-deals newsletter via the widget — on the site wholevoyage.com. WHY IT MATTERS Embed https://wholetech.com/newsletter/widget.js offering a monthly owner-direct deals digest: new villas, vessel listings, seasonal windows worth booking. An owned list converts repeat bookings without platform fees, and it is the natural upsell channel for partner featured placements once subscriber counts are honestly reportable. (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. | ||||
| 15 | 73 | Content | 2026-07-07 | on wholevoyage.com Deepen the main Hospitality guide with current data and examples |
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Deepen the main Hospitality guide with current data and examples — on the site 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 Hospitality 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 Hospitality. - 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. | ||||
| 16 | 73 | Revenue | 2026-07-07 | on wholevoyage.com Featured placements for real partner properties |
Offer homepage and destination-page featured slots to actual network partners, Sandalwood with SiteMinder deep links first, then thaivillaexchange owners as Robbie's photo sets land. Real properties, real booking paths, clearly labeled as featured. Partner inquiries route through a form that drafts a Gmail notification, never auto-sends. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Featured placements for real partner properties — on the site wholevoyage.com. WHY IT MATTERS Offer homepage and destination-page featured slots to actual network partners, Sandalwood with SiteMinder deep links first, then thaivillaexchange owners as Robbie's photo sets land. Real properties, real booking paths, clearly labeled as featured. Partner inquiries route through a form that drafts a Gmail notification, never auto-sends. (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. | ||||
| 17 | 68 | Design | 2026-07-11 | on wholevoyage.com Vintage steamship-line poster art direction |
Art-direct from golden-age voyage posters: cream paper ground, deep navy and gold rules, destination badges styled as luggage labels, and a compass-rose motif in navigation. It ties villas and vessels into one romantic brand world and instantly separates the hub from flat OTA-clone travel layouts. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Vintage steamship-line poster art direction — on the site wholevoyage.com. WHY IT MATTERS Art-direct from golden-age voyage posters: cream paper ground, deep navy and gold rules, destination badges styled as luggage labels, and a compass-rose motif in navigation. It ties villas and vessels into one romantic brand world and instantly separates the hub from flat OTA-clone travel layouts. (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. | ||||
| 18 | 67 | AEO | 2026-07-12 | on wholevoyage.com Lodging schema and book-direct FAQ answers |
Add TravelAgency schema for the hub and LodgingBusiness or BoatRental markup on property pages, with FAQPage entries answering 'how do I book a Thai villa directly with the owner'. Add sameAs links across the hospitality cluster and run af-deploy.py until the score sits 90-plus. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Lodging schema and book-direct FAQ answers — on the site wholevoyage.com. WHY IT MATTERS Add TravelAgency schema for the hub and LodgingBusiness or BoatRental markup on property pages, with FAQPage entries answering 'how do I book a Thai villa directly with the owner'. Add sameAs links across the hospitality cluster and run af-deploy.py until the score sits 90-plus. (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. | ||||
| 19 | 67 | Content | 2026-07-12 | on wholevoyage.com Add an FAQ answering the top questions in Hospitality |
Pull the real questions people ask in Hospitality and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Add an FAQ answering the top questions in Hospitality — on the site wholevoyage.com. WHY IT MATTERS Pull the real questions people ask in Hospitality and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Hospitality 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 Hospitality. - 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. | ||||
| 20 | 67 | Sources | 2026-07-12 | on wholevoyage.com Build /sources/ out to at least 10 authoritative links |
Only 0 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Build /sources/ out to at least 10 authoritative links — on the site 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 Hospitality. 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 Hospitality 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. | ||||
| 21 | 64 | Design | 2026-07-14 | on wholevoyage.com Boarding-pass cards and folio-styled property pages |
Style property and vessel summaries as boarding-pass cards, route, dates, berth or bedroom count in a perforated-edge card, with detail pages laid out like a hotel folio with itinerary rails down the margin. The travel-document metaphor makes listings scannable and gives screenshots a distinctive, shareable identity. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Boarding-pass cards and folio-styled property pages — on the site wholevoyage.com. WHY IT MATTERS Style property and vessel summaries as boarding-pass cards, route, dates, berth or bedroom count in a perforated-edge card, with detail pages laid out like a hotel folio with itinerary rails down the margin. The travel-document metaphor makes listings scannable and gives screenshots a distinctive, shareable identity. (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. | ||||
| 22 | 59 | Fresh | 2026-07-17 | on wholevoyage.com Add a /live/ news feed for Hospitality |
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Add a /live/ news feed for Hospitality — on the site 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 Hospitality: 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 Hospitality 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. | ||||
| 23 | 59 | Product | 2026-07-17 | on wholevoyage.com Cross-network availability strip on the hub |
Build a strip pulling live listings from thaivillaexchange and the HulloShips vessel exchange (hx service) onto the wholevoyage homepage: property name, region, next open window, direct link. The hub stops being a brochure and becomes a working front door to the network's real bookable inventory. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Cross-network availability strip on the hub — on the site wholevoyage.com. WHY IT MATTERS Build a strip pulling live listings from thaivillaexchange and the HulloShips vessel exchange (hx service) onto the wholevoyage homepage: property name, region, next open window, direct link. The hub stops being a brochure and becomes a working front door to the network's real bookable inventory. (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. | ||||
| 24 | 57 | SEO | 2026-07-19 | on wholevoyage.com Submit updated URLs via IndexNow and refresh the sitemap |
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site 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. | ||||
| 25 | 56 | Design | 2026-07-19 | on wholevoyage.com Apply a WT-Skins kit to lift the design and Agents-First score |
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. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site 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. | ||||
| 26 | 46 | SEO | 2026-07-26 | on wholevoyage.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Add Article + FAQ structured data — on the site 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. | ||||
| 27 | 43 | SEO | 2026-07-28 | on wholevoyage.com Strengthen internal links between the core, /sources/ and this worksheet |
A tight internal-link web spreads authority and keeps visitors moving through the site. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site 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. | ||||
| 28 | 40 | Video | 2026-07-31 | on wholevoyage.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Hospitality videos. Re-verify embeds. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site wholevoyage.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Hospitality videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Hospitality 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. | ||||
| 29 | 37 | Monetize | 2026-08-02 | on wholevoyage.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for wholevoyage.com You are working on ONE specific website: wholevoyage.com (live at https://wholevoyage.com/), a Hospitality site in the WholeTech network, served from /var/www/wholevoyage.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholevoyage.com and no other site — make all changes on wholevoyage.com. Act like a senior editor and web engineer who knows the Hospitality niche cold. GOAL (on wholevoyage.com) Add the network affiliate + AdSense setup — on the site wholevoyage.com. WHY IT MATTERS Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. 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. | ||||