A prioritized, living to-do list for austinretire.com, built from this site's sources and current trends in Retirement. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Flagship | 2026-06-19 | on austinretire.com Build the definitive Retirement cornerstone guide |
Create the single most useful, authoritative page on Retirement 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Build the definitive Retirement cornerstone guide — on the site austinretire.com. WHY IT MATTERS Create the single most useful, authoritative page on Retirement 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 Retirement — 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 Retirement resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 2 | 99 | Security | 2026-06-19 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site austinretire.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 | 98 | Security | 2026-06-20 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Lock down sensitive data — nothing private is publicly reachable — on the site austinretire.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. | ||||
| 4 | 95 | Security | 2026-06-22 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austinretire.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 | 92 | Flagship | 2026-06-24 | on austinretire.com Add an interactive tool and an email capture for Retirement |
Build one genuinely useful interactive element for Retirement (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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Add an interactive tool and an email capture for Retirement — on the site austinretire.com. WHY IT MATTERS Build one genuinely useful interactive element for Retirement (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 Retirement — 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 Retirement resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 91 | Flagship | 2026-06-25 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austinretire.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 Retirement — 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 Retirement resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 88 | Popularity | 2026-06-27 | on austinretire.com Downsizer neighborhood guides for walkability |
Profile neighborhoods through a downsizer lens, single-story stock, walkable groceries, hospital proximity, quiet streets, using observable facts and cited price context. Nobody else segments Austin neighborhoods for 70-year-olds; the gap is the opportunity. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Downsizer neighborhood guides for walkability — on the site austinretire.com. WHY IT MATTERS Profile neighborhoods through a downsizer lens, single-story stock, walkable groceries, hospital proximity, quiet streets, using observable facts and cited price context. Nobody else segments Austin neighborhoods for 70-year-olds; the gap is the opportunity. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 8 | 88 | Trends | 2026-06-27 | on austinretire.com Publish: The 2026 Social Security and Medicare changes to know |
Trending angle in Retirement. 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Publish: The 2026 Social Security and Medicare changes to know — on the site austinretire.com. WHY IT MATTERS Trending angle in Retirement. 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 Retirement 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 | 88 | Trends | 2026-06-27 | on austinretire.com Publish: Austin / Texas as a retirement destination — the real numbers |
Trending angle in Retirement. 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Publish: Austin / Texas as a retirement destination — the real numbers — on the site austinretire.com. WHY IT MATTERS Trending angle in Retirement. 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 Retirement 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 | 86 | Popularity | 2026-06-28 | on austinretire.com Cornerstone retiring-in-Austin guide set |
Build deep cornerstone guides: Texas tax picture for retirees including the over-65 homestead exemption, healthcare systems compared, and a directory of real 55+ communities with official links. Comprehensive sourced guides win the high-intent searches retirees actually make. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Cornerstone retiring-in-Austin guide set — on the site austinretire.com. WHY IT MATTERS Build deep cornerstone guides: Texas tax picture for retirees including the over-65 homestead exemption, healthcare systems compared, and a directory of real 55+ communities with official links. Comprehensive sourced guides win the high-intent searches retirees actually make. (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 | 83 | Popularity | 2026-06-30 | on austinretire.com Monthly senior events and resources roundup |
Publish a monthly roundup of genuinely useful happenings, senior center programs, AGE of Central Texas classes, library events, from official calendars, offered via the wholetech.com/newsletter/widget.js subscription embed. Gentle recurring service content builds trusted readership. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Monthly senior events and resources roundup — on the site austinretire.com. WHY IT MATTERS Publish a monthly roundup of genuinely useful happenings, senior center programs, AGE of Central Texas classes, library events, from official calendars, offered via the wholetech.com/newsletter/widget.js subscription embed. Gentle recurring service content builds trusted readership. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 12 | 82 | Trends | 2026-07-01 | on austinretire.com Publish: Downsizing and aging-in-place options |
Trending angle in Retirement. 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Publish: Downsizing and aging-in-place options — on the site austinretire.com. WHY IT MATTERS Trending angle in Retirement. 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 Retirement reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 81 | Revenue | 2026-07-02 | on austinretire.com Aging-in-place safety gear guides, Amazon tag |
Write careful guides to genuinely helpful home-safety gear, grab bars, motion-sensor night lighting, lever door handles, raised toilet seats, tagged colinfirthfan-20. Recommendations stay practical and modestly priced; trust-first tone, no fear-based selling to this audience. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Aging-in-place safety gear guides, Amazon tag — on the site austinretire.com. WHY IT MATTERS Write careful guides to genuinely helpful home-safety gear, grab bars, motion-sensor night lighting, lever door handles, raised toilet seats, tagged colinfirthfan-20. Recommendations stay practical and modestly priced; trust-first tone, no fear-based selling to this audience. (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 | 80 | Trends | 2026-07-03 | on austinretire.com Publish: Brain-health and staying-sharp routines |
Trending angle in Retirement. 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Publish: Brain-health and staying-sharp routines — on the site austinretire.com. WHY IT MATTERS Trending angle in Retirement. 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 Retirement 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. | ||||
| 15 | 76 | Revenue | 2026-07-05 | on austinretire.com Conservative AdSense with large-type placements |
Run shared AdSense pub-7759195213529699 sparingly, article pages only, never interrupting guide checklists, and keep placements clearly separated from content so nothing reads as advice. Restraint protects the trust this audience requires before anything converts. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Conservative AdSense with large-type placements — on the site austinretire.com. WHY IT MATTERS Run shared AdSense pub-7759195213529699 sparingly, article pages only, never interrupting guide checklists, and keep placements clearly separated from content so nothing reads as advice. Restraint protects the trust this audience requires before anything converts. (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 | Revenue | 2026-07-07 | on austinretire.com Travala links on scouting-visit guides |
On plan-your-scouting-trip guides for people considering an Austin retirement, include a labeled where-to-stay block with Travala hotel links near the neighborhoods being toured. Lodging for a real evaluation trip is honest, relevant monetization. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Travala links on scouting-visit guides — on the site austinretire.com. WHY IT MATTERS On plan-your-scouting-trip guides for people considering an Austin retirement, include a labeled where-to-stay block with Travala hotel links near the neighborhoods being toured. Lodging for a real evaluation trip is honest, relevant monetization. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 17 | 72 | Content | 2026-07-08 | on austinretire.com Deepen the main Retirement 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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Deepen the main Retirement guide with current data and examples — on the site austinretire.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 Retirement 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 Retirement. - 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. | ||||
| 18 | 71 | Design | 2026-07-09 | on austinretire.com Large-type porch-light warmth, dignified not beige |
Design for 70-year-old eyes with dignity: 19px-plus body type, high contrast, warm porch-light palette with Hill Country watercolor headers, and zero infantilizing clip art. Confident editorial design says respected reader, not patronized patient. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Large-type porch-light warmth, dignified not beige — on the site austinretire.com. WHY IT MATTERS Design for 70-year-old eyes with dignity: 19px-plus body type, high contrast, warm porch-light palette with Hill Country watercolor headers, and zero infantilizing clip art. Confident editorial design says respected reader, not patronized patient. (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. | ||||
| 19 | 69 | Design | 2026-07-10 | on austinretire.com Print-friendly guides with big contents cards |
Give every cornerstone guide a large tappable table-of-contents card block and a real print stylesheet, since this audience prints checklists and hands them to spouses. Designing for the print-and-discuss behavior is a feature competitors never consider. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Print-friendly guides with big contents cards — on the site austinretire.com. WHY IT MATTERS Give every cornerstone guide a large tappable table-of-contents card block and a real print stylesheet, since this audience prints checklists and hands them to spouses. Designing for the print-and-discuss behavior is a feature competitors never consider. (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 | 66 | AEO | 2026-07-12 | on austinretire.com Dated FAQs on taxes and retirement fit |
Add FAQ schema answering whether Austin suits retirement, the over-65 property-tax exemptions, and healthcare access, every answer citing official Travis CAD and state sources with visible dates. Keep both sitemaps current and run /root/af-deploy.py toward 90+. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Dated FAQs on taxes and retirement fit — on the site austinretire.com. WHY IT MATTERS Add FAQ schema answering whether Austin suits retirement, the over-65 property-tax exemptions, and healthcare access, every answer citing official Travis CAD and state sources with visible dates. Keep both sitemaps current and run /root/af-deploy.py toward 90+. (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. | ||||
| 21 | 66 | Content | 2026-07-12 | on austinretire.com Add an FAQ answering the top questions in Retirement |
Pull the real questions people ask in Retirement and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Add an FAQ answering the top questions in Retirement — on the site austinretire.com. WHY IT MATTERS Pull the real questions people ask in Retirement and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Retirement 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 Retirement. - 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. | ||||
| 22 | 58 | Product | 2026-07-18 | on austinretire.com Over-65 exemption checklist with official links |
Publish a step-by-step checklist for claiming Texas over-65 homestead exemptions, which Travis CAD forms, deadlines, what to bring, linking only official sources and stating plainly it is not legal advice. A concrete money-saving utility earns grateful shares. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Over-65 exemption checklist with official links — on the site austinretire.com. WHY IT MATTERS Publish a step-by-step checklist for claiming Texas over-65 homestead exemptions, which Travis CAD forms, deadlines, what to bring, linking only official sources and stating plainly it is not legal advice. A concrete money-saving utility earns grateful shares. (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 | Fresh | 2026-07-19 | on austinretire.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Retirement items and pinging IndexNow each run. ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Keep the live / news feed updated on cadence (2×/day) — on the site austinretire.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Retirement items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Retirement: 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 Retirement 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. | ||||
| 24 | 52 | SEO | 2026-07-22 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site austinretire.com. WHY IT MATTERS Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 47 | SEO | 2026-07-26 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site austinretire.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. | ||||
| 26 | 46 | SEO | 2026-07-26 | on austinretire.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Add Article + FAQ structured data — on the site austinretire.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 | 42 | Video | 2026-07-29 | on austinretire.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Retirement videos. Re-verify embeds. ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site austinretire.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Retirement videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Retirement videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 41 | Design | 2026-07-30 | on austinretire.com Audit against the Agents-First scorer (target 90+) |
Run the live AF scorer; close any gaps in clarity, links and machine-readability. ★ Copy-paste prompt for austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Audit against the Agents-First scorer (target 90+) — on the site austinretire.com. WHY IT MATTERS Run the live AF scorer; close any gaps in clarity, links and machine-readability. 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. | ||||
| 29 | 41 | Monetize | 2026-07-30 | on austinretire.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 austinretire.com You are working on ONE specific website: austinretire.com (live at https://austinretire.com/), a Retirement site in the WholeTech network, served from /var/www/austinretire.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinretire.com and no other site — make all changes on austinretire.com. Act like a senior editor and web engineer who knows the Retirement niche cold. GOAL (on austinretire.com) Verify affiliate links and ad placement resolve correctly — on the site austinretire.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. | ||||