A prioritized, living to-do list for austinrepeater.com, built from this site's sources and current trends in Ham Radio. 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 austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Lock down sensitive data — nothing private is publicly reachable — on the site austinrepeater.com. WHY IT MATTERS Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 2 | 99 | Security | 2026-06-19 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site austinrepeater.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 | 96 | Flagship | 2026-06-21 | on austinrepeater.com Build the definitive Ham Radio cornerstone guide |
Create the single most useful, authoritative page on Ham Radio 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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Build the definitive Ham Radio cornerstone guide — on the site austinrepeater.com. WHY IT MATTERS Create the single most useful, authoritative page on Ham Radio 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 Ham Radio — 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 Ham Radio 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. | ||||
| 4 | 96 | Security | 2026-06-21 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austinrepeater.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 | 93 | Flagship | 2026-06-23 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austinrepeater.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 Ham Radio — 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 Ham Radio 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 austinrepeater.com Add an interactive tool and an email capture for Ham Radio |
Build one genuinely useful interactive element for Ham Radio (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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Add an interactive tool and an email capture for Ham Radio — on the site austinrepeater.com. WHY IT MATTERS Build one genuinely useful interactive element for Ham Radio (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 Ham Radio — 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 Ham Radio 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 austinrepeater.com Publish: A current, data-backed explainer in Ham Radio |
Trending angle in Ham Radio. 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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Publish: A current, data-backed explainer in Ham Radio — on the site austinrepeater.com. WHY IT MATTERS Trending angle in Ham Radio. 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 Ham Radio 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 | 89 | Trends | 2026-06-26 | on austinrepeater.com Publish: The question your Ham Radio audience is searching most right now |
Trending angle in Ham Radio. 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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Publish: The question your Ham Radio audience is searching most right now — on the site austinrepeater.com. WHY IT MATTERS Trending angle in Ham Radio. 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 Ham Radio 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 | 87 | Popularity | 2026-06-28 | on austinrepeater.com Definitive sortable Austin repeater directory |
Build the canonical Central Texas repeater table: frequency, offset, PL tone, mode, coverage notes, sponsoring club, sourced from published club and coordination listings. Hams bookmark and forum-link authoritative directories for years; this is the site's flagship asset. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Definitive sortable Austin repeater directory — on the site austinrepeater.com. WHY IT MATTERS Build the canonical Central Texas repeater table: frequency, offset, PL tone, mode, coverage notes, sponsoring club, sourced from published club and coordination listings. Hams bookmark and forum-link authoritative directories for years; this is the site's flagship asset. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 85 | Popularity | 2026-06-29 | on austinrepeater.com Weekly nets schedule reference page |
Maintain a schedule of Austin-area weekly nets, day, time, frequency, sponsoring club, from published club pages. Net check-ins are the hobby's recurring social ritual, so a reliable schedule page earns repeat weekly visits and mentions on the air. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Weekly nets schedule reference page — on the site austinrepeater.com. WHY IT MATTERS Maintain a schedule of Austin-area weekly nets, day, time, frequency, sponsoring club, from published club pages. Net check-ins are the hobby's recurring social ritual, so a reliable schedule page earns repeat weekly visits and mentions on the air. (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 austinrepeater.com License exam study path and session calendar |
Publish Technician-to-Extra study guides plus a calendar of real Austin-area VE exam sessions from published ARRL and Laurel VEC listings, refreshed monthly. Every new local ham passes through exactly this search funnel on their way into the hobby. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) License exam study path and session calendar — on the site austinrepeater.com. WHY IT MATTERS Publish Technician-to-Extra study guides plus a calendar of real Austin-area VE exam sessions from published ARRL and Laurel VEC listings, refreshed monthly. Every new local ham passes through exactly this search funnel on their way into the hobby. (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 | 81 | Revenue | 2026-07-02 | on austinrepeater.com Beginner radio buying guides with Amazon tag |
Write honest first-radio guides, budget handhelds versus Yaesu and Icom, roll-up J-pole antennas, programming cables, tagged colinfirthfan-20. New Technicians buy a handheld within days of passing; meeting that moment with plain advice is the natural revenue engine. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Beginner radio buying guides with Amazon tag — on the site austinrepeater.com. WHY IT MATTERS Write honest first-radio guides, budget handhelds versus Yaesu and Icom, roll-up J-pole antennas, programming cables, tagged colinfirthfan-20. New Technicians buy a handheld within days of passing; meeting that moment with plain advice is the natural revenue engine. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 81 | Trends | 2026-07-02 | on austinrepeater.com Publish: A 'what changed in 2026' round-up for Ham Radio |
Trending angle in Ham Radio. 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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Publish: A 'what changed in 2026' round-up for Ham Radio — on the site austinrepeater.com. WHY IT MATTERS Trending angle in Ham Radio. 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 Ham Radio reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 14 | 76 | Revenue | 2026-07-05 | on austinrepeater.com Go-box and antenna project parts lists |
Publish build guides for popular projects, portable go-boxes, dual-band base antennas, with complete Amazon-tagged parts lists using colinfirthfan-20. Project content earns links from club newsletters while monetizing through parts hams would buy anyway. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Go-box and antenna project parts lists — on the site austinrepeater.com. WHY IT MATTERS Publish build guides for popular projects, portable go-boxes, dual-band base antennas, with complete Amazon-tagged parts lists using colinfirthfan-20. Project content earns links from club newsletters while monetizing through parts hams would buy anyway. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 15 | 72 | Content | 2026-07-08 | on austinrepeater.com Deepen the main Ham Radio 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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Deepen the main Ham Radio guide with current data and examples — on the site austinrepeater.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 Ham Radio 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 Ham Radio. - 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. | ||||
| 16 | 70 | Revenue | 2026-07-10 | on austinrepeater.com AdSense on study and project pages |
Run shared AdSense pub-7759195213529699 on exam-study and project-build templates, keeping the repeater directory itself ad-free so it prints cleanly and stays the trusted reference clubs link from their own sites. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) AdSense on study and project pages — on the site austinrepeater.com. WHY IT MATTERS Run shared AdSense pub-7759195213529699 on exam-study and project-build templates, keeping the repeater directory itself ad-free so it prints cleanly and stays the trusted reference clubs link from their own sites. (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 | 68 | Content | 2026-07-11 | on austinrepeater.com Add an FAQ answering the top questions in Ham Radio |
Pull the real questions people ask in Ham Radio and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Add an FAQ answering the top questions in Ham Radio — on the site austinrepeater.com. WHY IT MATTERS Pull the real questions people ask in Ham Radio and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Ham Radio 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 Ham Radio. - 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 | 68 | Design | 2026-07-11 | on austinrepeater.com Directory styled as channel-memory display |
Render the repeater table like a transceiver's memory-channel screen: dark background, green-on-black seven-segment-style frequency column, tone and offset in labeled fields. Hams instantly parse the radio-native layout, and it becomes the screenshot that identifies the site. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Directory styled as channel-memory display — on the site austinrepeater.com. WHY IT MATTERS Render the repeater table like a transceiver's memory-channel screen: dark background, green-on-black seven-segment-style frequency column, tone and offset in labeled fields. Hams instantly parse the radio-native layout, and it becomes the screenshot that identifies the site. (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 | 67 | Design | 2026-07-12 | on austinrepeater.com VFO-dial and schematic field-manual aesthetic |
Art-direct from the shack: smoked-amber VFO frequency readouts in monospace, PCB-trace divider lines, schematic-symbol icons for section markers, olive-drab go-box panel textures. The site should look like a well-organized operating position, not a generic hobby blog. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) VFO-dial and schematic field-manual aesthetic — on the site austinrepeater.com. WHY IT MATTERS Art-direct from the shack: smoked-amber VFO frequency readouts in monospace, PCB-trace divider lines, schematic-symbol icons for section markers, olive-drab go-box panel textures. The site should look like a well-organized operating position, not a generic hobby blog. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 65 | AEO | 2026-07-13 | on austinrepeater.com Ham licensing FAQs with schema and citations |
Add FAQ schema answering how to get licensed in Texas, what repeaters cover Austin, and what a new Technician can do, citing FCC and ARRL sources. Run /root/af-deploy.py toward 90+ and keep both sitemaps plus the IndexNow key active. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Ham licensing FAQs with schema and citations — on the site austinrepeater.com. WHY IT MATTERS Add FAQ schema answering how to get licensed in Texas, what repeaters cover Austin, and what a new Technician can do, citing FCC and ARRL sources. Run /root/af-deploy.py toward 90+ and keep both sitemaps plus the IndexNow key active. (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 | 63 | Product | 2026-07-14 | on austinrepeater.com Downloadable CHIRP-ready repeater CSV |
Export the directory as a CHIRP-format CSV so new hams program every Austin repeater into a handheld in one import, versioned with a date and changelog. A genuinely useful file download is the sharable artifact that spreads through clubs and Reddit. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Downloadable CHIRP-ready repeater CSV — on the site austinrepeater.com. WHY IT MATTERS Export the directory as a CHIRP-format CSV so new hams program every Austin repeater into a handheld in one import, versioned with a date and changelog. A genuinely useful file download is the sharable artifact that spreads through clubs and Reddit. (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 | 59 | Design | 2026-07-17 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site austinrepeater.com. WHY IT MATTERS The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s. HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 23 | 56 | Fresh | 2026-07-19 | on austinrepeater.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Ham Radio items and pinging IndexNow each run. ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Keep the live / news feed updated on cadence (2×/day) — on the site austinrepeater.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Ham Radio items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Ham Radio: 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 Ham Radio 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 | 54 | SEO | 2026-07-21 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site austinrepeater.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 | 49 | SEO | 2026-07-24 | on austinrepeater.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Add Article + FAQ structured data — on the site austinrepeater.com. WHY IT MATTERS Schema.org markup earns richer results and helps answer-engines cite the page correctly. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 26 | 44 | SEO | 2026-07-28 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site austinrepeater.com. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 27 | 42 | Monetize | 2026-07-29 | on austinrepeater.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 austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Verify affiliate links and ad placement resolve correctly — on the site austinrepeater.com. WHY IT MATTERS Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 40 | Video | 2026-07-31 | on austinrepeater.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Ham Radio videos. Re-verify embeds. ★ Copy-paste prompt for austinrepeater.com You are working on ONE specific website: austinrepeater.com (live at https://austinrepeater.com/), a Ham Radio site in the WholeTech network, served from /var/www/austinrepeater.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinrepeater.com and no other site — make all changes on austinrepeater.com. Act like a senior editor and web engineer who knows the Ham Radio niche cold. GOAL (on austinrepeater.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site austinrepeater.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Ham Radio videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Ham Radio 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. | ||||