A prioritized, living to-do list for dotepp.com, built from this site's sources and current trends in Domains. 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 dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Lock down sensitive data — nothing private is publicly reachable — on the site dotepp.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 dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site dotepp.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 | 97 | Security | 2026-06-21 | on dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site dotepp.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 | 96 | Flagship | 2026-06-21 | on dotepp.com Build the definitive Domains cornerstone guide |
Create the single most useful, authoritative page on Domains 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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Build the definitive Domains cornerstone guide — on the site dotepp.com. WHY IT MATTERS Create the single most useful, authoritative page on Domains 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 Domains — 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 Domains 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 | 92 | Flagship | 2026-06-24 | on dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site dotepp.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 Domains — 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 Domains 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 | 91 | Flagship | 2026-06-25 | on dotepp.com Add an interactive tool and an email capture for Domains |
Build one genuinely useful interactive element for Domains (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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Add an interactive tool and an email capture for Domains — on the site dotepp.com. WHY IT MATTERS Build one genuinely useful interactive element for Domains (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 Domains — 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 Domains 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 | 91 | Popularity | 2026-06-25 | on dotepp.com Replace parked page with warm personal hub |
A parked or placeholder name domain earns nothing and ranks for nothing. Build dotepp.com as Dorothy 'Dot' Epp's genuine personal hub — short bio she approves, a few photos, how to reach the family — so anyone searching her name finds her own page first, not data-broker listings. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Replace parked page with warm personal hub — on the site dotepp.com. WHY IT MATTERS A parked or placeholder name domain earns nothing and ranks for nothing. Build dotepp.com as Dorothy 'Dot' Epp's genuine personal hub — short bio she approves, a few photos, how to reach the family — so anyone searching her name finds her own page first, not data-broker listings. (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 | 89 | Trends | 2026-06-26 | on dotepp.com Publish: A current, data-backed explainer in Domains |
Trending angle in Domains. 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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Publish: A current, data-backed explainer in Domains — on the site dotepp.com. WHY IT MATTERS Trending angle in Domains. 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 Domains 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 | 89 | Trends | 2026-06-26 | on dotepp.com Publish: The question your Domains audience is searching most right now |
Trending angle in Domains. 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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Publish: The question your Domains audience is searching most right now — on the site dotepp.com. WHY IT MATTERS Trending angle in Domains. 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 Domains 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 | Trends | 2026-06-29 | on dotepp.com Publish: A 'what changed in 2026' round-up for Domains |
Trending angle in Domains. 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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Publish: A 'what changed in 2026' round-up for Domains — on the site dotepp.com. WHY IT MATTERS Trending angle in Domains. 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 Domains 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 | 84 | Popularity | 2026-06-30 | on dotepp.com One evergreen page on something Dot loves |
Sit with Dot and capture one page on a subject she genuinely cares about — in her words, at her pace. Authentic personal pages earn shares from family and friends that no generated content can, and the process itself is a good afternoon. Nothing invented; only what she offers. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) One evergreen page on something Dot loves — on the site dotepp.com. WHY IT MATTERS Sit with Dot and capture one page on a subject she genuinely cares about — in her words, at her pace. Authentic personal pages earn shares from family and friends that no generated content can, and the process itself is a good afternoon. Nothing invented; only what she offers. (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 | Popularity | 2026-07-01 | on dotepp.com GSC, both sitemaps, and IndexNow basics |
Verify the domain in Search Console alongside the network's other properties, generate /sitemap.xml plus /sitemap/index.html per the two-sitemaps rule, and drop the IndexNow key at the webroot. A personal name site's whole job is being findable; these three plumbing items are what make it so. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) GSC, both sitemaps, and IndexNow basics — on the site dotepp.com. WHY IT MATTERS Verify the domain in Search Console alongside the network's other properties, generate /sitemap.xml plus /sitemap/index.html per the two-sitemaps rule, and drop the IndexNow key at the webroot. A personal name site's whole job is being findable; these three plumbing items are what make it so. (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. | ||||
| 13 | 79 | Revenue | 2026-07-03 | on dotepp.com Dot's picks page with Amazon tag |
Only if Dot enjoys curating it: a small 'things I actually use' page — books, kitchen or garden tools she vouches for — with Associates tag colinfirthfan-20 and plain one-line reasons in her voice. Gentle, honest, and entirely optional; skip it if it feels like work to her. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Dot's picks page with Amazon tag — on the site dotepp.com. WHY IT MATTERS Only if Dot enjoys curating it: a small 'things I actually use' page — books, kitchen or garden tools she vouches for — with Associates tag colinfirthfan-20 and plain one-line reasons in her voice. Gentle, honest, and entirely optional; skip it if it feels like work to her. (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 | 78 | Revenue | 2026-07-04 | on dotepp.com Tasteful page for the house and shop sale |
Paul and Dot are selling their Cedar Creek house and shop. A quiet, well-photographed page on Dot's own domain — the story of the place, honest details, an inquiry form producing draft notifications only — is genuine revenue support for the family's largest pending transaction, with zero pressure tactics. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Tasteful page for the house and shop sale — on the site dotepp.com. WHY IT MATTERS Paul and Dot are selling their Cedar Creek house and shop. A quiet, well-photographed page on Dot's own domain — the story of the place, honest details, an inquiry form producing draft notifications only — is genuine revenue support for the family's largest pending transaction, with zero pressure tactics. (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 | 74 | Revenue | 2026-07-07 | on dotepp.com Places-we-loved travel page with Travala |
A short page of places Paul and Dot have genuinely enjoyed, each with a line of memory and a Travala booking link from the network's live affiliate integration. Warm, true, and lightly monetized — the tone a personal site can carry that a commercial travel site cannot. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Places-we-loved travel page with Travala — on the site dotepp.com. WHY IT MATTERS A short page of places Paul and Dot have genuinely enjoyed, each with a line of memory and a Travala booking link from the network's live affiliate integration. Warm, true, and lightly monetized — the tone a personal site can carry that a commercial travel site cannot. (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 | 70 | Content | 2026-07-10 | on dotepp.com Deepen the main Domains 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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Deepen the main Domains guide with current data and examples — on the site dotepp.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 Domains 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 Domains. - 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. | ||||
| 17 | 68 | Design | 2026-07-11 | on dotepp.com Photo section as deckle-edged scrapbook |
Present family photos as a scrapbook spread: deckle-edged frames, handwritten-style captions, corner-mount details, one or two photos per row so each gets room to breathe. The album format honors the material and keeps the page calm and easy to navigate at any age. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Photo section as deckle-edged scrapbook — on the site dotepp.com. WHY IT MATTERS Present family photos as a scrapbook spread: deckle-edged frames, handwritten-style captions, corner-mount details, one or two photos per row so each gets room to breathe. The album format honors the material and keeps the page calm and easy to navigate at any age. (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 dotepp.com Person schema to disambiguate Dot's identity |
Add Person markup — name, spouse, location, sameAs to her real profiles — so agents and search engines resolve 'Dot Epp' to her own page. The Nancy Bergeron mailer mixup showed how easily identities blur online; explicit schema on her own domain is the durable fix. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Person schema to disambiguate Dot's identity — on the site dotepp.com. WHY IT MATTERS Add Person markup — name, spouse, location, sameAs to her real profiles — so agents and search engines resolve 'Dot Epp' to her own page. The Nancy Bergeron mailer mixup showed how easily identities blur online; explicit schema on her own domain is the durable fix. (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 | Design | 2026-07-12 | on dotepp.com Letterpress stationery and pressed-flower aesthetic |
Design the site like Dot's personal stationery: cream paper texture, a classic hand-set serif, botanical line drawings as section ornaments, and generous margins. Large readable type throughout. It should feel like a letter from her, not a template — dignified, warm, and unmistakably personal. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Letterpress stationery and pressed-flower aesthetic — on the site dotepp.com. WHY IT MATTERS Design the site like Dot's personal stationery: cream paper texture, a classic hand-set serif, botanical line drawings as section ornaments, and generous margins. Large readable type throughout. It should feel like a letter from her, not a template — dignified, warm, and unmistakably personal. (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 | 65 | Content | 2026-07-13 | on dotepp.com Add an FAQ answering the top questions in Domains |
Pull the real questions people ask in Domains and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Add an FAQ answering the top questions in Domains — on the site dotepp.com. WHY IT MATTERS Pull the real questions people ask in Domains and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Domains 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 Domains. - 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 dotepp.com Simple family links and contact page |
A plain page linking the family's sites — Paul's walhus.com, Shey's sheyroth.com — with a contact form that creates draft notifications for review rather than sending anything automatically. It makes dotepp.com the family's stable front door without exposing email addresses to scrapers. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Simple family links and contact page — on the site dotepp.com. WHY IT MATTERS A plain page linking the family's sites — Paul's walhus.com, Shey's sheyroth.com — with a contact form that creates draft notifications for review rather than sending anything automatically. It makes dotepp.com the family's stable front door without exposing email addresses to scrapers. (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 | 58 | Design | 2026-07-18 | on dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site dotepp.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. | ||||
| 23 | 56 | SEO | 2026-07-19 | on dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site dotepp.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. | ||||
| 24 | 54 | Fresh | 2026-07-21 | on dotepp.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Domains items and pinging IndexNow each run. ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Keep the live / news feed updated on cadence (2×/day) — on the site dotepp.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Domains items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Domains: 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 Domains 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 | 48 | SEO | 2026-07-25 | on dotepp.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Add Article + FAQ structured data — on the site dotepp.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. | ||||
| 26 | 48 | SEO | 2026-07-25 | on dotepp.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 dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site dotepp.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. | ||||
| 27 | 42 | Monetize | 2026-07-29 | on dotepp.com Verify affiliate links and ad placement resolve correctly |
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Verify affiliate links and ad placement resolve correctly — on the site dotepp.com. WHY IT MATTERS Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 42 | Video | 2026-07-29 | on dotepp.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Domains videos. Re-verify embeds. ★ Copy-paste prompt for dotepp.com You are working on ONE specific website: dotepp.com (live at https://dotepp.com/), a Domains site in the WholeTech network, served from /var/www/dotepp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for dotepp.com and no other site — make all changes on dotepp.com. Act like a senior editor and web engineer who knows the Domains niche cold. GOAL (on dotepp.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site dotepp.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Domains videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Domains 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. | ||||