A prioritized, living to-do list for wholetech.com, built from this site's sources and current trends in Network Hub. 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 | Flagship | 2026-06-19 | on wholetech.com Build the definitive Network Hub cornerstone guide |
Create the single most useful, authoritative page on Network Hub 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Build the definitive Network Hub cornerstone guide — on the site wholetech.com. WHY IT MATTERS Create the single most useful, authoritative page on Network Hub 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 Network Hub — 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 Network Hub 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. | ||||
| 2 | 99 | Security | 2026-06-19 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Lock down sensitive data — nothing private is publicly reachable — on the site wholetech.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. | ||||
| 3 | 97 | Security | 2026-06-21 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site wholetech.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. | ||||
| 4 | 97 | Security | 2026-06-21 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site wholetech.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. | ||||
| 5 | 95 | Flagship | 2026-06-22 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site wholetech.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 Network Hub — 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 Network Hub 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 | 95 | Flagship | 2026-06-22 | on wholetech.com Add an interactive tool and an email capture for Network Hub |
Build one genuinely useful interactive element for Network Hub (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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Add an interactive tool and an email capture for Network Hub — on the site wholetech.com. WHY IT MATTERS Build one genuinely useful interactive element for Network Hub (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 Network Hub — 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 Network Hub 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 | 93 | Trends | 2026-06-23 | on wholetech.com Publish: A current, data-backed explainer in Network Hub |
Trending angle in Network Hub. 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Publish: A current, data-backed explainer in Network Hub — on the site wholetech.com. WHY IT MATTERS Trending angle in Network Hub. 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 Network Hub 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. | ||||
| 8 | 89 | Popularity | 2026-06-26 | on wholetech.com Monthly state-of-the-network traffic report |
Publish a monthly report built from the real AWStats /api/stats.json pipeline: top-20 site leaderboard, biggest movers, one lesson learned. Honest numbers from a 280-site independent network are rare and genuinely citable by indie-web and SEO writers. Permalink each month, announce via the network promo bar. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Monthly state-of-the-network traffic report — on the site wholetech.com. WHY IT MATTERS Publish a monthly report built from the real AWStats /api/stats.json pipeline: top-20 site leaderboard, biggest movers, one lesson learned. Honest numbers from a 280-site independent network are rare and genuinely citable by indie-web and SEO writers. Permalink each month, announce via the network promo bar. (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. | ||||
| 9 | 85 | Popularity | 2026-06-29 | on wholetech.com Publish the Agents-First rubric as public methodology |
Turn the af-deploy.py scoring rubric into a public methodology page under /rules/: what agents need from a site, how the 0-100 score works, before/after examples from the network. Webmasters chasing agent-readiness will cite and link it, positioning wholetech.com as the reference for the Agents-First idea. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Publish the Agents-First rubric as public methodology — on the site wholetech.com. WHY IT MATTERS Turn the af-deploy.py scoring rubric into a public methodology page under /rules/: what agents need from a site, how the 0-100 score works, before/after examples from the network. Webmasters chasing agent-readiness will cite and link it, positioning wholetech.com as the reference for the Agents-First idea. (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. | ||||
| 10 | 83 | Trends | 2026-06-30 | on wholetech.com Publish: The question your Network Hub audience is searching most right now |
Trending angle in Network Hub. 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Publish: The question your Network Hub audience is searching most right now — on the site wholetech.com. WHY IT MATTERS Trending angle in Network Hub. 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 Network Hub 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. | ||||
| 11 | 82 | Revenue | 2026-07-01 | on wholetech.com Hub-to-studio referral path into atxengine.com |
Add a quiet 'built by the studio' strip on the report and webdev pages linking to atxengine.com with a project-inquiry form that drafts a Gmail notification, never auto-sends. The hub's proof-of-work (280 live sites, public dashboards) is the sales asset; route the credibility somewhere it can earn. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Hub-to-studio referral path into atxengine.com — on the site wholetech.com. WHY IT MATTERS Add a quiet 'built by the studio' strip on the report and webdev pages linking to atxengine.com with a project-inquiry form that drafts a Gmail notification, never auto-sends. The hub's proof-of-work (280 live sites, public dashboards) is the sales asset; route the credibility somewhere it can earn. (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 | 82 | Trends | 2026-07-01 | on wholetech.com Publish: A 'what changed in 2026' round-up for Network Hub |
Trending angle in Network Hub. 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Publish: A 'what changed in 2026' round-up for Network Hub — on the site wholetech.com. WHY IT MATTERS Trending angle in Network Hub. 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 Network Hub 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 | 79 | Popularity | 2026-07-03 | on wholetech.com Wire sitemap.wholetech.com sections into GSC and IndexNow |
The homepage is deliberately not a directory, so make sitemap.wholetech.com pull that weight: submit every section sitemap in GSC, and batch-ping IndexNow after each nightly regeneration so new session logs, worksheets, and reports index within hours instead of weeks. Cheap, mechanical, compounding discovery. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Wire sitemap.wholetech.com sections into GSC and IndexNow — on the site wholetech.com. WHY IT MATTERS The homepage is deliberately not a directory, so make sitemap.wholetech.com pull that weight: submit every section sitemap in GSC, and batch-ping IndexNow after each nightly regeneration so new session logs, worksheets, and reports index within hours instead of weeks. Cheap, mechanical, compounding discovery. (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 | 77 | Revenue | 2026-07-05 | on wholetech.com Monetize the webdev guide with AdSense and books |
The /webdev guide is the hub's most outsider-friendly content. Enable AdSense pub-7759195213529699 on guide chapters and add an honest 'books and gear that actually helped' shelf via colinfirthfan-20. Keep dashboards and worksheets ad-free so the operational pages stay clean and fast. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Monetize the webdev guide with AdSense and books — on the site wholetech.com. WHY IT MATTERS The /webdev guide is the hub's most outsider-friendly content. Enable AdSense pub-7759195213529699 on guide chapters and add an honest 'books and gear that actually helped' shelf via colinfirthfan-20. Keep dashboards and worksheets ad-free so the operational pages stay clean and fast. (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 | 76 | Revenue | 2026-07-05 | on wholetech.com Network digest newsletter with future sponsor slot |
Embed https://wholetech.com/newsletter/widget.js on the report and webdev pages offering a monthly network digest. Once the list has real subscribers, add one clearly-labeled sponsor slot; state actual list size when pitching, never inflated. Owned audience also de-risks the whole network against search volatility. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Network digest newsletter with future sponsor slot — on the site wholetech.com. WHY IT MATTERS Embed https://wholetech.com/newsletter/widget.js on the report and webdev pages offering a monthly network digest. Once the list has real subscribers, add one clearly-labeled sponsor slot; state actual list size when pitching, never inflated. Owned audience also de-risks the whole network against search volatility. (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. | ||||
| 16 | 72 | Design | 2026-07-08 | on wholetech.com Mission-control NOC aesthetic for the hub |
Art-direct wholetech.com as a network operations center: dark console panels, status-LED dots fed by live stats.json and sec/ data, monospace readouts, and a constellation map rendering all 280 domains as linked nodes on the homepage. The hub should visibly be the control room it actually is. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Mission-control NOC aesthetic for the hub — on the site wholetech.com. WHY IT MATTERS Art-direct wholetech.com as a network operations center: dark console panels, status-LED dots fed by live stats.json and sec/ data, monospace readouts, and a constellation map rendering all 280 domains as linked nodes on the homepage. The hub should visibly be the control room it actually is. (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. | ||||
| 17 | 72 | Sources | 2026-07-08 | on wholetech.com Build /sources/ out to at least 10 authoritative links |
Only 4 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Build /sources/ out to at least 10 authoritative links — on the site wholetech.com. WHY IT MATTERS Only 4 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 Network Hub. 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 Network Hub 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. | ||||
| 18 | 70 | Content | 2026-07-10 | on wholetech.com Deepen the main Network Hub 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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Deepen the main Network Hub guide with current data and examples — on the site wholetech.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 Network Hub 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 Network Hub. - 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. | ||||
| 19 | 70 | Design | 2026-07-10 | on wholetech.com One token set unifying all worksheet pages |
Alldomains, stats, sec, diskspace, godaddy, and header-conflicts each drifted visually. Define one WT-Skins hub kit (type scale, table styling, chip colors, sticky-header treatment) and apply it across every worksheet so the whole admin surface reads as one instrument panel rather than a dozen one-off tables. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) One token set unifying all worksheet pages — on the site wholetech.com. WHY IT MATTERS Alldomains, stats, sec, diskspace, godaddy, and header-conflicts each drifted visually. Define one WT-Skins hub kit (type scale, table styling, chip colors, sticky-header treatment) and apply it across every worksheet so the whole admin surface reads as one instrument panel rather than a dozen one-off tables. (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. | ||||
| 20 | 69 | Content | 2026-07-10 | on wholetech.com Add an FAQ answering the top questions in Network Hub |
Pull the real questions people ask in Network Hub and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Add an FAQ answering the top questions in Network Hub — on the site wholetech.com. WHY IT MATTERS Pull the real questions people ask in Network Hub and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Network Hub 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 Network Hub. - 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. | ||||
| 21 | 64 | Product | 2026-07-14 | on wholetech.com Public /status/ page merging health dashboards |
Combine sec/, diskspace/, and stats into one public /status/ page: uptime posture, SSL health, disk headroom, traffic pulse. A transparent status page is itself a popularity asset (people link to networks that show their guts) and a trust signal for studio prospects evaluating whether the operation is real. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Public /status/ page merging health dashboards — on the site wholetech.com. WHY IT MATTERS Combine sec/, diskspace/, and stats into one public /status/ page: uptime posture, SSL health, disk headroom, traffic pulse. A transparent status page is itself a popularity asset (people link to networks that show their guts) and a trust signal for studio prospects evaluating whether the operation is real. (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. | ||||
| 22 | 61 | AEO | 2026-07-16 | on wholetech.com Organization schema plus sameAs identity graph |
Add Organization schema naming WholeTech with sameAs links to github.com/paulwalhus and x.com/springnet, plus an FAQPage answering 'what is the WholeTech network' and 'who builds these sites' with institutional bylines. As the flagship, this page anchors the entity graph agents use to connect all 280 properties. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Organization schema plus sameAs identity graph — on the site wholetech.com. WHY IT MATTERS Add Organization schema naming WholeTech with sameAs links to github.com/paulwalhus and x.com/springnet, plus an FAQPage answering 'what is the WholeTech network' and 'who builds these sites' with institutional bylines. As the flagship, this page anchors the entity graph agents use to connect all 280 properties. (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. | ||||
| 23 | 58 | Design | 2026-07-18 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site wholetech.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. | ||||
| 24 | 58 | Fresh | 2026-07-18 | on wholetech.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Network Hub items and pinging IndexNow each run. ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Keep the live / news feed updated on cadence (2×/day) — on the site wholetech.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Network Hub items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Network Hub: 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 Network Hub 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. | ||||
| 25 | 52 | SEO | 2026-07-22 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site wholetech.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. | ||||
| 26 | 46 | SEO | 2026-07-26 | on wholetech.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Add Article + FAQ structured data — on the site wholetech.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 | 45 | Video | 2026-07-27 | on wholetech.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Network Hub videos. Re-verify embeds. ★ Copy-paste prompt for wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site wholetech.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Network Hub videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Network Hub 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. | ||||
| 28 | 44 | SEO | 2026-07-28 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site wholetech.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. | ||||
| 29 | 42 | Monetize | 2026-07-29 | on wholetech.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 wholetech.com You are working on ONE specific website: wholetech.com (live at https://wholetech.com/), a Network Hub site in the WholeTech network, served from /var/www/wholetech.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wholetech.com and no other site — make all changes on wholetech.com. Act like a senior editor and web engineer who knows the Network Hub niche cold. GOAL (on wholetech.com) Add the network affiliate + AdSense setup — on the site wholetech.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. | ||||