A prioritized, living to-do list for atxfans.com, built from this site's sources and current trends in Austin Sports. 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 atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site atxfans.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. | ||||
| 2 | 96 | Flagship | 2026-06-21 | on atxfans.com Build the definitive Austin Sports cornerstone guide |
Create the single most useful, authoritative page on Austin Sports 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Build the definitive Austin Sports cornerstone guide — on the site atxfans.com. WHY IT MATTERS Create the single most useful, authoritative page on Austin Sports 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 Austin Sports — 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 Austin Sports resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 3 | 96 | Security | 2026-06-21 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Lock down sensitive data — nothing private is publicly reachable — on the site atxfans.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 | Flagship | 2026-06-22 | on atxfans.com Add an interactive tool and an email capture for Austin Sports |
Build one genuinely useful interactive element for Austin Sports (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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Add an interactive tool and an email capture for Austin Sports — on the site atxfans.com. WHY IT MATTERS Build one genuinely useful interactive element for Austin Sports (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 Austin Sports — 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 Austin Sports 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 | 94 | Security | 2026-06-23 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site atxfans.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. | ||||
| 6 | 93 | Flagship | 2026-06-23 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site atxfans.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 Austin Sports — 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 Austin Sports resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 91 | Trends | 2026-06-25 | on atxfans.com Publish: A current, data-backed explainer in Austin Sports |
Trending angle in Austin Sports. 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Publish: A current, data-backed explainer in Austin Sports — on the site atxfans.com. WHY IT MATTERS Trending angle in Austin Sports. 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 Austin Sports reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 8 | 87 | Popularity | 2026-06-28 | on atxfans.com Own the Austin watch-party bar directory |
Build a sortable guide to where Austin watches — Austin FC bars, Longhorns hangouts, Cowboys and Texans splits — with neighborhood, screens, and sound policy from the venues' published info, refreshed each season. Where-to-watch is the highest-intent fan query no schedule site answers. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Own the Austin watch-party bar directory — on the site atxfans.com. WHY IT MATTERS Build a sortable guide to where Austin watches — Austin FC bars, Longhorns hangouts, Cowboys and Texans splits — with neighborhood, screens, and sound policy from the venues' published info, refreshed each season. Where-to-watch is the highest-intent fan query no schedule site answers. (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 | 87 | Popularity | 2026-06-28 | on atxfans.com Game-day guides for every Austin FC home match |
Publish a guide per Q2 Stadium match — parking and transit, supporter-section culture, La Murga traditions — updated from club and CapMetro public pages. Matchday logistics searches spike reliably every home fixture, and evergreen guides re-rank each cycle with small refreshes. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Game-day guides for every Austin FC home match — on the site atxfans.com. WHY IT MATTERS Publish a guide per Q2 Stadium match — parking and transit, supporter-section culture, La Murga traditions — updated from club and CapMetro public pages. Matchday logistics searches spike reliably every home fixture, and evergreen guides re-rank each cycle with small refreshes. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 87 | Trends | 2026-06-28 | on atxfans.com Publish: The question your Austin Sports audience is searching most right now |
Trending angle in Austin Sports. 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Publish: The question your Austin Sports audience is searching most right now — on the site atxfans.com. WHY IT MATTERS Trending angle in Austin Sports. 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 Austin Sports reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 84 | Popularity | 2026-06-30 | on atxfans.com Fan-culture explainers, not scores |
Differentiate from schedule sites with culture pieces: Los Verdes and Austin Anthem histories, the Longhorns game-day ritual glossary, why Austin has no NFL team. Culture content earns social shares and supporter-group links that pure fixture pages never attract — and it never goes stale. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Fan-culture explainers, not scores — on the site atxfans.com. WHY IT MATTERS Differentiate from schedule sites with culture pieces: Los Verdes and Austin Anthem histories, the Longhorns game-day ritual glossary, why Austin has no NFL team. Culture content earns social shares and supporter-group links that pure fixture pages never attract — and it never goes stale. (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 | 84 | Trends | 2026-06-30 | on atxfans.com Publish: A 'what changed in 2026' round-up for Austin Sports |
Trending angle in Austin Sports. 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Publish: A 'what changed in 2026' round-up for Austin Sports — on the site atxfans.com. WHY IT MATTERS Trending angle in Austin Sports. 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 Austin Sports 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 | 77 | Revenue | 2026-07-05 | on atxfans.com Amazon fan-gear guides per team |
Curate verde-and-black Austin FC gear, burnt-orange tailgate equipment, and jersey-care picks with the colinfirthfan-20 tag, each with a genuine one-line reason. Gear guides tied to specific fandoms convert far better than generic sports-shop links and slot naturally under culture content. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Amazon fan-gear guides per team — on the site atxfans.com. WHY IT MATTERS Curate verde-and-black Austin FC gear, burnt-orange tailgate equipment, and jersey-care picks with the colinfirthfan-20 tag, each with a genuine one-line reason. Gear guides tied to specific fandoms convert far better than generic sports-shop links and slot naturally under culture 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. | ||||
| 14 | 76 | Revenue | 2026-07-05 | on atxfans.com TicketNetwork placements on game-preview pages |
The TicketNetwork affiliate is live on the network's sports sites — extend it here with clearly-labeled resale-ticket modules on match and game preview pages. Preview pages catch fans at decision moment; label resale honestly and link the official box office alongside per the honest-monetization rule. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) TicketNetwork placements on game-preview pages — on the site atxfans.com. WHY IT MATTERS The TicketNetwork affiliate is live on the network's sports sites — extend it here with clearly-labeled resale-ticket modules on match and game preview pages. Preview pages catch fans at decision moment; label resale honestly and link the official box office alongside per the honest-monetization rule. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 15 | 74 | Revenue | 2026-07-07 | on atxfans.com AdSense on guides, clean on the bar directory |
Run pub-7759195213529699 on game-day and culture pages while keeping the watch-party directory table ad-free so it stays the shareable, screenshot-friendly asset. The directory builds the audience; the guides monetize it — do not blur the two. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) AdSense on guides, clean on the bar directory — on the site atxfans.com. WHY IT MATTERS Run pub-7759195213529699 on game-day and culture pages while keeping the watch-party directory table ad-free so it stays the shareable, screenshot-friendly asset. The directory builds the audience; the guides monetize it — do not blur the two. (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 atxfans.com Deepen the main Austin Sports 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Deepen the main Austin Sports guide with current data and examples — on the site atxfans.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 Austin Sports 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 Austin Sports. - 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 | 69 | Design | 2026-07-10 | on atxfans.com Supporter-section aesthetic: tifo banners, scarf typography |
Art-direct from the stands: section headers as two-pole tifo banner shapes, a knitted-scarf stripe motif for dividers in verde, black, and burnt orange, and bold condensed chant-style typography. It should feel like the south end of Q2, not a sports-news template. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Supporter-section aesthetic: tifo banners, scarf typography — on the site atxfans.com. WHY IT MATTERS Art-direct from the stands: section headers as two-pole tifo banner shapes, a knitted-scarf stripe motif for dividers in verde, black, and burnt orange, and bold condensed chant-style typography. It should feel like the south end of Q2, not a sports-news template. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 18 | 67 | Content | 2026-07-12 | on atxfans.com Add an FAQ answering the top questions in Austin Sports |
Pull the real questions people ask in Austin Sports and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Add an FAQ answering the top questions in Austin Sports — on the site atxfans.com. WHY IT MATTERS Pull the real questions people ask in Austin Sports and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Austin Sports 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 Austin Sports. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 19 | 67 | Sources | 2026-07-12 | on atxfans.com Build /sources/ out to at least 10 authoritative links |
Only 2 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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Build /sources/ out to at least 10 authoritative links — on the site atxfans.com. WHY IT MATTERS Only 2 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 Austin Sports. 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 Austin Sports 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. | ||||
| 20 | 66 | Design | 2026-07-12 | on atxfans.com Scoreboard-style data blocks for fixtures |
Render schedules and standings in stadium-scoreboard styling — LED-dot matrix numerals, black housing cards, amber time displays. Fixture data is unavoidable commodity content; presenting it in scoreboard hardware language makes even the commodity parts feel owned. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Scoreboard-style data blocks for fixtures — on the site atxfans.com. WHY IT MATTERS Render schedules and standings in stadium-scoreboard styling — LED-dot matrix numerals, black housing cards, amber time displays. Fixture data is unavoidable commodity content; presenting it in scoreboard hardware language makes even the commodity parts feel owned. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 63 | AEO | 2026-07-14 | on atxfans.com Event schema on matches, FAQ on logistics |
Mark fixtures with SportsEvent JSON-LD and add FAQPage covering where to park at Q2 Stadium, can you bring bags, and where Austin FC fans watch away matches. Logistics questions dominate voice and answer-engine sports queries locally; verify 90-plus with af-deploy.py. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Event schema on matches, FAQ on logistics — on the site atxfans.com. WHY IT MATTERS Mark fixtures with SportsEvent JSON-LD and add FAQPage covering where to park at Q2 Stadium, can you bring bags, and where Austin FC fans watch away matches. Logistics questions dominate voice and answer-engine sports queries locally; verify 90-plus with af-deploy.py. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 62 | Popularity | 2026-07-15 | on atxfans.com Coordinate with the gamesked ticket feed |
Consume the existing gamesked.com feed.json infrastructure to surface Austin-relevant fixtures automatically, cross-linking both directions across the network's fifteen calendar sites. Shared plumbing keeps schedules accurate without manual upkeep and concentrates the sports cluster's internal authority on the Austin pages. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Coordinate with the gamesked ticket feed — on the site atxfans.com. WHY IT MATTERS Consume the existing gamesked.com feed.json infrastructure to surface Austin-relevant fixtures automatically, cross-linking both directions across the network's fifteen calendar sites. Shared plumbing keeps schedules accurate without manual upkeep and concentrates the sports cluster's internal authority on the Austin pages. (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 | 59 | Design | 2026-07-17 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site atxfans.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 | 57 | Fresh | 2026-07-19 | on atxfans.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Austin Sports items and pinging IndexNow each run. ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Keep the live / news feed updated on cadence (2×/day) — on the site atxfans.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Austin Sports items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Austin Sports: 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 Austin Sports items on schedule and is discovered quickly. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 54 | SEO | 2026-07-21 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site atxfans.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 | 49 | SEO | 2026-07-24 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site atxfans.com. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 27 | 47 | SEO | 2026-07-26 | on atxfans.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Add Article + FAQ structured data — on the site atxfans.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. | ||||
| 28 | 44 | Video | 2026-07-28 | on atxfans.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Sports videos. Re-verify embeds. ★ Copy-paste prompt for atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site atxfans.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Sports videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Austin Sports 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 | 39 | Monetize | 2026-07-31 | on atxfans.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 atxfans.com You are working on ONE specific website: atxfans.com (live at https://atxfans.com/), a Austin Sports site in the WholeTech network, served from /var/www/atxfans.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxfans.com and no other site — make all changes on atxfans.com. Act like a senior editor and web engineer who knows the Austin Sports niche cold. GOAL (on atxfans.com) Verify affiliate links and ad placement resolve correctly — on the site atxfans.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. | ||||