A prioritized, living to-do list for baylesshigh.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 | 99 | Security | 2026-06-19 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Lock down sensitive data — nothing private is publicly reachable — on the site baylesshigh.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 baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site baylesshigh.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. | ||||
| 3 | 97 | Security | 2026-06-21 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site baylesshigh.com. WHY IT MATTERS Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 4 | 96 | Flagship | 2026-06-21 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Build the definitive Family History cornerstone guide — on the site baylesshigh.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. | ||||
| 5 | 96 | Flagship | 2026-06-21 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site baylesshigh.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. | ||||
| 6 | 94 | Flagship | 2026-06-23 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Add an interactive tool and an email capture for Family History — on the site baylesshigh.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 | 89 | Trends | 2026-06-26 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Publish: A current, data-backed explainer in Family History — on the site baylesshigh.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 | 88 | Popularity | 2026-06-27 | on baylesshigh.com Class-year index pages built for reunion searches |
Create one page per graduating class with the yearbook-era photos and memorabilia the site can lawfully display, names indexed as text. Alumni search their class year before every reunion cycle; class-index pages are the door through which entire graduating classes discover and share the archive. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Class-year index pages built for reunion searches — on the site baylesshigh.com. WHY IT MATTERS Create one page per graduating class with the yearbook-era photos and memorabilia the site can lawfully display, names indexed as text. Alumni search their class year before every reunion cycle; class-index pages are the door through which entire graduating classes discover and share the archive. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 9 | 86 | Trends | 2026-06-28 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Publish: The question your Family History audience is searching most right now — on the site baylesshigh.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. | ||||
| 10 | 84 | Popularity | 2026-06-30 | on baylesshigh.com Then-and-now campus history from public records |
Publish a building-by-building history — construction dates, renovations, the campus as students knew it by decade — sourced from district records and newspaper archives, paired with then-and-now photos. Institutional memory pages get shared across alumni Facebook groups and linked by local historical societies. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Then-and-now campus history from public records — on the site baylesshigh.com. WHY IT MATTERS Publish a building-by-building history — construction dates, renovations, the campus as students knew it by decade — sourced from district records and newspaper archives, paired with then-and-now photos. Institutional memory pages get shared across alumni Facebook groups and linked by local historical societies. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 81 | Revenue | 2026-07-02 | on baylesshigh.com Yearbook-scanning and preservation gear via Amazon |
Publish a 'digitize your yearbooks and photos' guide — flatbed scanners suited to bound books, photo-safe storage, negative digitizers — tagged colinfirthfan-20. Alumni holding aging yearbooks are exactly the audience with this need, and the guide serves the archive's preservation mission while monetizing honestly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Yearbook-scanning and preservation gear via Amazon — on the site baylesshigh.com. WHY IT MATTERS Publish a 'digitize your yearbooks and photos' guide — flatbed scanners suited to bound books, photo-safe storage, negative digitizers — tagged colinfirthfan-20. Alumni holding aging yearbooks are exactly the audience with this need, and the guide serves the archive's preservation mission while monetizing honestly. (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 | 80 | Popularity | 2026-07-03 | on baylesshigh.com Alumni memory submissions feeding a stories page |
Add a memory-submission form — teacher tributes, game recollections, hallway stories — that generates drafted Gmail notifications for review before anything publishes, never auto-posting. Reader-contributed stories are self-renewing content, and every contributor becomes a promoter who sends classmates to see their own memory published. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Alumni memory submissions feeding a stories page — on the site baylesshigh.com. WHY IT MATTERS Add a memory-submission form — teacher tributes, game recollections, hallway stories — that generates drafted Gmail notifications for review before anything publishes, never auto-posting. Reader-contributed stories are self-renewing content, and every contributor becomes a promoter who sends classmates to see their own memory published. (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 | 80 | Trends | 2026-07-03 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Publish: A 'what changed in 2026' round-up for Family History — on the site baylesshigh.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. | ||||
| 14 | 79 | Revenue | 2026-07-03 | on baylesshigh.com AdSense on history and class-index pages |
Run pub-7759195213529699 on the campus-history and class-year index pages where nostalgic search traffic arrives from reunion-season queries. Alumni-demographic display inventory performs steadily and predictably; keep density light and hold placements entirely out of memorial-style content so the archive preserves its respectful, keepsake character throughout. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) AdSense on history and class-index pages — on the site baylesshigh.com. WHY IT MATTERS Run pub-7759195213529699 on the campus-history and class-year index pages where nostalgic search traffic arrives from reunion-season queries. Alumni-demographic display inventory performs steadily and predictably; keep density light and hold placements entirely out of memorial-style content so the archive preserves its respectful, keepsake character throughout. (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 | 72 | Revenue | 2026-07-08 | on baylesshigh.com Flat-rate reunion venue and vendor listings |
Offer paid flat-rate listings for reunion-relevant local businesses — banquet venues, caterers, photographers — on a reunions resource page, with inquiries arriving as drafted Gmail notifications. Reunion committees actively shop these services; clearly-labeled sponsored listings monetize that intent without touching the archival content. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Flat-rate reunion venue and vendor listings — on the site baylesshigh.com. WHY IT MATTERS Offer paid flat-rate listings for reunion-relevant local businesses — banquet venues, caterers, photographers — on a reunions resource page, with inquiries arriving as drafted Gmail notifications. Reunion committees actively shop these services; clearly-labeled sponsored listings monetize that intent without touching the archival content. (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 baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Deepen the main Family History guide with current data and examples — on the site baylesshigh.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 | 70 | Sources | 2026-07-10 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Build /sources/ out to at least 10 authoritative links — on the site baylesshigh.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. | ||||
| 18 | 67 | AEO | 2026-07-12 | on baylesshigh.com FAQ schema on school history basics |
Add FAQPage schema answering 'when was Bayless High School founded,' 'what are the school colors,' and 'when are class reunions' with sourced answer blocks, plus historical EducationalOrganization markup. Run af-deploy.py to 90+ so alumni asking assistants about the school get this archive quoted. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) FAQ schema on school history basics — on the site baylesshigh.com. WHY IT MATTERS Add FAQPage schema answering 'when was Bayless High School founded,' 'what are the school colors,' and 'when are class reunions' with sourced answer blocks, plus historical EducationalOrganization markup. Run af-deploy.py to 90+ so alumni asking assistants about the school get this archive quoted. (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 baylesshigh.com Yearbook aesthetic with halftone photos and signatures |
Art-direct as a mid-century yearbook: halftone-screened photo treatment, school-color duotone spreads, headings in yearbook-title lettering, and handwriting-style 'stay cool, see you this summer' signature accents in the margins. The object alumni already treasure becomes the interface — instantly warm, instantly recognizable. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Yearbook aesthetic with halftone photos and signatures — on the site baylesshigh.com. WHY IT MATTERS Art-direct as a mid-century yearbook: halftone-screened photo treatment, school-color duotone spreads, headings in yearbook-title lettering, and handwriting-style 'stay cool, see you this summer' signature accents in the margins. The object alumni already treasure becomes the interface — instantly warm, instantly recognizable. (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 baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Add an FAQ answering the top questions in Family History — on the site baylesshigh.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. | ||||
| 21 | 65 | Design | 2026-07-13 | on baylesshigh.com Notable-alumni grid styled as trophy case |
Present distinguished alumni as a glass trophy-case display — engraved-plate name labels, wood-shelf framing, medal and plaque iconography for verifiable achievements only. The trophy case was the school's own storytelling furniture; reusing it honors the tradition and keeps the section from feeling like a LinkedIn wall. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Notable-alumni grid styled as trophy case — on the site baylesshigh.com. WHY IT MATTERS Present distinguished alumni as a glass trophy-case display — engraved-plate name labels, wood-shelf framing, medal and plaque iconography for verifiable achievements only. The trophy case was the school's own storytelling furniture; reusing it honors the tradition and keeps the section from feeling like a LinkedIn wall. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 60 | Product | 2026-07-17 | on baylesshigh.com Sortable class-and-era worksheet across decades |
Build an alldomains-model worksheet listing every graduating class as a sortable row — year, class size where documented, reunion status, link to its index page. It doubles as a completeness dashboard showing which decades still need scanning, and gives visiting alumni a one-glance map of the whole archive. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Sortable class-and-era worksheet across decades — on the site baylesshigh.com. WHY IT MATTERS Build an alldomains-model worksheet listing every graduating class as a sortable row — year, class size where documented, reunion status, link to its index page. It doubles as a completeness dashboard showing which decades still need scanning, and gives visiting alumni a one-glance map of the whole archive. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 23 | 57 | Design | 2026-07-19 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site baylesshigh.com. WHY IT MATTERS The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s. HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 24 | 54 | Fresh | 2026-07-21 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Keep the live / news feed updated on cadence (2×/day) — on the site baylesshigh.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 | 53 | SEO | 2026-07-21 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site baylesshigh.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 | 48 | SEO | 2026-07-25 | on baylesshigh.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Add Article + FAQ structured data — on the site baylesshigh.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 | 48 | SEO | 2026-07-25 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site baylesshigh.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 | Video | 2026-07-28 | on baylesshigh.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 baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site baylesshigh.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. | ||||
| 29 | 38 | Monetize | 2026-08-01 | on baylesshigh.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for baylesshigh.com You are working on ONE specific website: baylesshigh.com (live at https://baylesshigh.com/), a Family History site in the WholeTech network, served from /var/www/baylesshigh.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for baylesshigh.com and no other site — make all changes on baylesshigh.com. Act like a senior editor and web engineer who knows the Family History niche cold. GOAL (on baylesshigh.com) Add the network affiliate + AdSense setup — on the site baylesshigh.com. WHY IT MATTERS Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||