A prioritized, living to-do list for sheyroth.com, built from this site's sources and current trends in Family History. 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 | 98 | Security | 2026-06-20 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Lock down sensitive data — nothing private is publicly reachable — on the site sheyroth.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 | 97 | Flagship | 2026-06-21 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site sheyroth.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 Family History — 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 Family History 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. | ||||
| 3 | 97 | Security | 2026-06-21 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site sheyroth.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 | Security | 2026-06-21 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site sheyroth.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. | ||||
| 5 | 95 | Flagship | 2026-06-22 | on sheyroth.com Build the definitive Family History cornerstone guide |
Create the single most useful, authoritative page on Family History 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Build the definitive Family History cornerstone guide — on the site sheyroth.com. WHY IT MATTERS Create the single most useful, authoritative page on Family History 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 Family History — 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 Family History 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 | 90 | Flagship | 2026-06-26 | on sheyroth.com Add an interactive tool and an email capture for Family History |
Build one genuinely useful interactive element for Family History (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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Add an interactive tool and an email capture for Family History — on the site sheyroth.com. WHY IT MATTERS Build one genuinely useful interactive element for Family History (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 Family History — 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 Family History resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 88 | Trends | 2026-06-27 | on sheyroth.com Publish: The question your Family History audience is searching most right now |
Trending angle in Family History. 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Publish: The question your Family History audience is searching most right now — on the site sheyroth.com. WHY IT MATTERS Trending angle in Family History. 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 Family History 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 | 87 | Trends | 2026-06-28 | on sheyroth.com Publish: A current, data-backed explainer in Family History |
Trending angle in Family History. 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Publish: A current, data-backed explainer in Family History — on the site sheyroth.com. WHY IT MATTERS Trending angle in Family History. 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 Family History 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 | 85 | Popularity | 2026-06-29 | on sheyroth.com Build Shey's electronic press kit page |
Create the EPK promoters actually look for: bio, press photos, set formats, and booking contact — every fact sourced directly from Shey, nothing invented. An EPK is the page that gets a DJ booked and shared; it should be the site's most polished, most linkable surface. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Build Shey's electronic press kit page — on the site sheyroth.com. WHY IT MATTERS Create the EPK promoters actually look for: bio, press photos, set formats, and booking contact — every fact sourced directly from Shey, nothing invented. An EPK is the page that gets a DJ booked and shared; it should be the site's most polished, most linkable surface. (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 | 85 | Trends | 2026-06-29 | on sheyroth.com Publish: A 'what changed in 2026' round-up for Family History |
Trending angle in Family History. 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Publish: A 'what changed in 2026' round-up for Family History — on the site sheyroth.com. WHY IT MATTERS Trending angle in Family History. 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 Family History 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 | Popularity | 2026-07-01 | on sheyroth.com Gig calendar with permalink per date |
List past and upcoming gigs from Shey's real schedule, each date a permalink naming venue and city. Venue-name pages accumulate local search presence over time, and an archived gig history is the credibility trail talent buyers scan before booking an unfamiliar DJ. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Gig calendar with permalink per date — on the site sheyroth.com. WHY IT MATTERS List past and upcoming gigs from Shey's real schedule, each date a permalink naming venue and city. Venue-name pages accumulate local search presence over time, and an archived gig history is the credibility trail talent buyers scan before booking an unfamiliar DJ. (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 sheyroth.com Embed Shey's real mixes on a verified videos page |
Gather links to wherever Shey actually publishes sets and mixes, and embed them on the site plus a /videos/ page with every embed verified through check-embed.mjs. Nothing sells a DJ like the sound itself; only ever embed his genuine output, never filler mixes. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Embed Shey's real mixes on a verified videos page — on the site sheyroth.com. WHY IT MATTERS Gather links to wherever Shey actually publishes sets and mixes, and embed them on the site plus a /videos/ page with every embed verified through check-embed.mjs. Nothing sells a DJ like the sound itself; only ever embed his genuine output, never filler mixes. (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 | 82 | Revenue | 2026-07-01 | on sheyroth.com Booking inquiry form with draft-only notifications |
Add a booking form capturing event type, date, location, and budget range, generating DRAFT notifications only — never auto-sent email. Booking fees are the site's real revenue path, and structured inquiries mean Shey responds to qualified requests instead of vague DM threads. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Booking inquiry form with draft-only notifications — on the site sheyroth.com. WHY IT MATTERS Add a booking form capturing event type, date, location, and budget range, generating DRAFT notifications only — never auto-sent email. Booking fees are the site's real revenue path, and structured inquiries mean Shey responds to qualified requests instead of vague DM threads. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 14 | 76 | Revenue | 2026-07-05 | on sheyroth.com Shey's rig gear page with real equipment |
Publish the gear Shey genuinely performs with — controller, headphones, laptop stand — as told by him, with colinfirthfan-20 Amazon links and no invented endorsements. Aspiring DJs constantly search working DJs' setups; honest rig pages convert well and cost one conversation to source. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Shey's rig gear page with real equipment — on the site sheyroth.com. WHY IT MATTERS Publish the gear Shey genuinely performs with — controller, headphones, laptop stand — as told by him, with colinfirthfan-20 Amazon links and no invented endorsements. Aspiring DJs constantly search working DJs' setups; honest rig pages convert well and cost one conversation to source. (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 sheyroth.com Rate-anchoring book-Shey services page |
Publish a services page describing set formats and typical lengths — club set, private event, extended set — with 'quote on request' rather than invented prices. Anchoring the offer converts curious visitors into form submissions and filters out inquiries that were never real bookings. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Rate-anchoring book-Shey services page — on the site sheyroth.com. WHY IT MATTERS Publish a services page describing set formats and typical lengths — club set, private event, extended set — with 'quote on request' rather than invented prices. Anchoring the offer converts curious visitors into form submissions and filters out inquiries that were never real bookings. (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 | 73 | Content | 2026-07-07 | on sheyroth.com Deepen the main Family History 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Deepen the main Family History guide with current data and examples — on the site sheyroth.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 Family History 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 Family History. - 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 | 72 | Design | 2026-07-08 | on sheyroth.com Neon club-flyer art direction |
Design from rave-poster DNA: high-contrast neon on black, halftone-treated photography, bold condensed poster type, and a subtle scanline shimmer on the hero. The site should look like the flyer for Shey's next night — unmistakably a DJ's page from the first frame. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Neon club-flyer art direction — on the site sheyroth.com. WHY IT MATTERS Design from rave-poster DNA: high-contrast neon on black, halftone-treated photography, bold condensed poster type, and a subtle scanline shimmer on the hero. The site should look like the flyer for Shey's next night — unmistakably a DJ's page from the first frame. (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 | 69 | Sources | 2026-07-10 | on sheyroth.com Build /sources/ out to at least 10 authoritative links |
Only 3 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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Build /sources/ out to at least 10 authoritative links — on the site sheyroth.com. WHY IT MATTERS Only 3 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 Family History. 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 Family History 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. | ||||
| 19 | 68 | Content | 2026-07-11 | on sheyroth.com Add an FAQ answering the top questions in Family History |
Pull the real questions people ask in Family History and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Add an FAQ answering the top questions in Family History — on the site sheyroth.com. WHY IT MATTERS Pull the real questions people ask in Family History and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Family History 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 Family History. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 67 | Design | 2026-07-12 | on sheyroth.com Mix cards styled as vinyl labels |
Render each embedded mix as a spinning-record card — circular vinyl-label artwork with the mix title in label type, plus genre and BPM chips around the rim. It makes the mixes page feel like flipping through a crate, on-theme and instantly screenshot-worthy. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Mix cards styled as vinyl labels — on the site sheyroth.com. WHY IT MATTERS Render each embedded mix as a spinning-record card — circular vinyl-label artwork with the mix title in label type, plus genre and BPM chips around the rim. It makes the mixes page feel like flipping through a crate, on-theme and instantly screenshot-worthy. (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. | ||||
| 21 | 66 | AEO | 2026-07-12 | on sheyroth.com Person and Event schema for booking queries |
Add Person plus PerformingGroup schema for Shey and Event markup on each gig-calendar entry, so 'DJ Shey Roth booking' queries return structured contact and upcoming-date information to agents and search. Keep every schema fact sourced from Shey; run af-deploy.py afterward. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Person and Event schema for booking queries — on the site sheyroth.com. WHY IT MATTERS Add Person plus PerformingGroup schema for Shey and Event markup on each gig-calendar entry, so 'DJ Shey Roth booking' queries return structured contact and upcoming-date information to agents and search. Keep every schema fact sourced from Shey; run af-deploy.py afterward. (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 | Design | 2026-07-16 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site sheyroth.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 | 60 | Product | 2026-07-17 | on sheyroth.com Enforce the private raw-directory guard |
The /raw directory is private local-only and must never deploy. Verify the server carries no /raw, add an exclusion to the deploy script, and add a post-push check that fails loudly if it ever appears. Protecting Shey's private material is a hard product requirement of this site. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Enforce the private raw-directory guard — on the site sheyroth.com. WHY IT MATTERS The /raw directory is private local-only and must never deploy. Verify the server carries no /raw, add an exclusion to the deploy script, and add a post-push check that fails loudly if it ever appears. Protecting Shey's private material is a hard product requirement of this site. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 24 | 54 | Fresh | 2026-07-21 | on sheyroth.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Family History items and pinging IndexNow each run. ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Keep the live / news feed updated on cadence (2×/day) — on the site sheyroth.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Family History items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Family History: 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 Family History 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 | 54 | SEO | 2026-07-21 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site sheyroth.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 | 52 | SEO | 2026-07-22 | on sheyroth.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Add Article + FAQ structured data — on the site sheyroth.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 | SEO | 2026-07-27 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site sheyroth.com. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 44 | Monetize | 2026-07-28 | on sheyroth.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 sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Verify affiliate links and ad placement resolve correctly — on the site sheyroth.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. | ||||
| 29 | 40 | Video | 2026-07-31 | on sheyroth.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Family History videos. Re-verify embeds. ★ Copy-paste prompt for sheyroth.com You are working on ONE specific website: sheyroth.com (live at https://sheyroth.com/), a Family History site in the WholeTech network, served from /var/www/sheyroth.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for sheyroth.com and no other site — make all changes on sheyroth.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on sheyroth.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site sheyroth.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Family History videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Family History 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. | ||||