A prioritized, living to-do list for austinhangout.com, built from this site's sources and current trends in Austin Hangouts. 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 austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Lock down sensitive data — nothing private is publicly reachable — on the site austinhangout.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 austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austinhangout.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. | ||||
| 3 | 95 | Flagship | 2026-06-22 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austinhangout.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 Hangouts — 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 Hangouts 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 | 94 | Security | 2026-06-23 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site austinhangout.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. | ||||
| 5 | 93 | Flagship | 2026-06-23 | on austinhangout.com Build the definitive Austin Hangouts cornerstone guide |
Create the single most useful, authoritative page on Austin Hangouts 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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Build the definitive Austin Hangouts cornerstone guide — on the site austinhangout.com. WHY IT MATTERS Create the single most useful, authoritative page on Austin Hangouts 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 Hangouts — 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 Hangouts 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 | 92 | Flagship | 2026-06-24 | on austinhangout.com Add an interactive tool and an email capture for Austin Hangouts |
Build one genuinely useful interactive element for Austin Hangouts (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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Add an interactive tool and an email capture for Austin Hangouts — on the site austinhangout.com. WHY IT MATTERS Build one genuinely useful interactive element for Austin Hangouts (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 Hangouts — 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 Hangouts resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 89 | Trends | 2026-06-26 | on austinhangout.com Publish: A current, data-backed explainer in Austin Hangouts |
Trending angle in Austin Hangouts. 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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Publish: A current, data-backed explainer in Austin Hangouts — on the site austinhangout.com. WHY IT MATTERS Trending angle in Austin Hangouts. 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 Hangouts 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 austinhangout.com Vibe-based hangout finder guide pages |
Build guides organized by vibe rather than geography: dog-friendly patios, laptop-tolerant afternoons, first-date spots, late-night after midnight. Vibe queries are how people actually search for hangouts, and each guide gives listed venues a reason to share it. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Vibe-based hangout finder guide pages — on the site austinhangout.com. WHY IT MATTERS Build guides organized by vibe rather than geography: dog-friendly patios, laptop-tolerant afternoons, first-date spots, late-night after midnight. Vibe queries are how people actually search for hangouts, and each guide gives listed venues a reason to share it. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 9 | 86 | Trends | 2026-06-28 | on austinhangout.com Publish: The question your Austin Hangouts audience is searching most right now |
Trending angle in Austin Hangouts. 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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Publish: The question your Austin Hangouts audience is searching most right now — on the site austinhangout.com. WHY IT MATTERS Trending angle in Austin Hangouts. 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 Hangouts reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 85 | Popularity | 2026-06-29 | on austinhangout.com Expand Best of Austin 2026 into category pages |
Break the existing best-of-2026 page into one page per category, patios, dive bars, late-night eats, each written in the site's own critique voice with original commentary, never mirroring copyrighted ballot text. Category pages catch specific best-of searches the single page cannot. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Expand Best of Austin 2026 into category pages — on the site austinhangout.com. WHY IT MATTERS Break the existing best-of-2026 page into one page per category, patios, dive bars, late-night eats, each written in the site's own critique voice with original commentary, never mirroring copyrighted ballot text. Category pages catch specific best-of searches the single page cannot. (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 | 84 | Popularity | 2026-06-30 | on austinhangout.com Walk-through videos of iconic Austin hangouts |
Add a /videos/ page embedding real walk-through and tour footage of famous Austin spots, verifying every embed with check-embed.mjs and dropping non-embeddable IDs. Pair each clip with a short honest blurb so video searchers land on genuinely useful pages. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Walk-through videos of iconic Austin hangouts — on the site austinhangout.com. WHY IT MATTERS Add a /videos/ page embedding real walk-through and tour footage of famous Austin spots, verifying every embed with check-embed.mjs and dropping non-embeddable IDs. Pair each clip with a short honest blurb so video searchers land on genuinely useful 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. | ||||
| 12 | 80 | Trends | 2026-07-03 | on austinhangout.com Publish: A 'what changed in 2026' round-up for Austin Hangouts |
Trending angle in Austin Hangouts. 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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Publish: A 'what changed in 2026' round-up for Austin Hangouts — on the site austinhangout.com. WHY IT MATTERS Trending angle in Austin Hangouts. 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 Hangouts 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 | 79 | Revenue | 2026-07-03 | on austinhangout.com TicketNetwork links for venue show calendars |
Where a hangout is also a live-music venue, Continental Club, Mohawk class rooms, list upcoming ticketed shows with Impact TicketNetwork resale links, clearly disclosed. Show intent rides naturally on venue pages and extends the network's existing live integration. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) TicketNetwork links for venue show calendars — on the site austinhangout.com. WHY IT MATTERS Where a hangout is also a live-music venue, Continental Club, Mohawk class rooms, list upcoming ticketed shows with Impact TicketNetwork resale links, clearly disclosed. Show intent rides naturally on venue pages and extends the network's existing live integration. (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 | 73 | Revenue | 2026-07-07 | on austinhangout.com Travala stay links on visitor itineraries |
Create weekend-visitor itineraries, 48 hours in East Austin, and include a labeled where-to-stay block with Travala hotel links near each route. Tourist readers need lodging; embedding it in genuinely useful itineraries keeps the monetization honest. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Travala stay links on visitor itineraries — on the site austinhangout.com. WHY IT MATTERS Create weekend-visitor itineraries, 48 hours in East Austin, and include a labeled where-to-stay block with Travala hotel links near each route. Tourist readers need lodging; embedding it in genuinely useful itineraries keeps the monetization honest. (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 | 70 | Content | 2026-07-10 | on austinhangout.com Deepen the main Austin Hangouts 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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Deepen the main Austin Hangouts guide with current data and examples — on the site austinhangout.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 Hangouts 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 Hangouts. - 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 austinhangout.com AdSense on category and vibe guide pages |
Place shared AdSense pub-7759195213529699 units on the best-of category and vibe guide templates where research sessions run long, keeping itinerary pages cleaner so the affiliate blocks there remain the single clear call to action. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) AdSense on category and vibe guide pages — on the site austinhangout.com. WHY IT MATTERS Place shared AdSense pub-7759195213529699 units on the best-of category and vibe guide templates where research sessions run long, keeping itinerary pages cleaner so the affiliate blocks there remain the single clear call to action. (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 | 67 | Design | 2026-07-12 | on austinhangout.com Dusk patio palette with neon script accents |
Art-direct from an Austin patio at dusk: string-light bokeh header treatment, neon-sign script for section titles, picnic-table wood grain panel textures, and a palette of Barton Springs green, limestone, and sunset orange. It should feel like 7pm on Rainey Street. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Dusk patio palette with neon script accents — on the site austinhangout.com. WHY IT MATTERS Art-direct from an Austin patio at dusk: string-light bokeh header treatment, neon-sign script for section titles, picnic-table wood grain panel textures, and a palette of Barton Springs green, limestone, and sunset orange. It should feel like 7pm on Rainey Street. (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 | 66 | Content | 2026-07-12 | on austinhangout.com Add an FAQ answering the top questions in Austin Hangouts |
Pull the real questions people ask in Austin Hangouts and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Add an FAQ answering the top questions in Austin Hangouts — on the site austinhangout.com. WHY IT MATTERS Pull the real questions people ask in Austin Hangouts and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Austin Hangouts 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 Hangouts. - 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 | 66 | Design | 2026-07-12 | on austinhangout.com Filter chips styled as drink coasters |
Render the vibe filters, patio, late-night, dog-friendly, live music, as round cardboard drink-coaster chips with letterpress icons, stacking slightly when multiple are active. A tactile bar-table metaphor turns a utilitarian filter row into the site's signature interaction. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Filter chips styled as drink coasters — on the site austinhangout.com. WHY IT MATTERS Render the vibe filters, patio, late-night, dog-friendly, live music, as round cardboard drink-coaster chips with letterpress icons, stacking slightly when multiple are active. A tactile bar-table metaphor turns a utilitarian filter row into the site's signature interaction. (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 | 63 | Product | 2026-07-14 | on austinhangout.com Sortable hangout worksheet with practical columns |
Build a master alldomains-style table of every covered spot: neighborhood, vibe tags, patio, food, typical crowd, late hours, sortable with search chips and row-to-card detail. One practical reference table converts casual readers into repeat bookmark users. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Sortable hangout worksheet with practical columns — on the site austinhangout.com. WHY IT MATTERS Build a master alldomains-style table of every covered spot: neighborhood, vibe tags, patio, food, typical crowd, late hours, sortable with search chips and row-to-card detail. One practical reference table converts casual readers into repeat bookmark users. (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 | 61 | AEO | 2026-07-16 | on austinhangout.com Best-patio FAQs with cited, dated answers |
Publish FAQ blocks answering best patios, best dive bars, and where to hang out tonight in Austin, each answer citing the relevant guide with a visible updated date. Add schema, keep both sitemaps fresh, and run /root/af-deploy.py toward 90+. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Best-patio FAQs with cited, dated answers — on the site austinhangout.com. WHY IT MATTERS Publish FAQ blocks answering best patios, best dive bars, and where to hang out tonight in Austin, each answer citing the relevant guide with a visible updated date. Add schema, keep both sitemaps fresh, and run /root/af-deploy.py toward 90+. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 59 | Fresh | 2026-07-17 | on austinhangout.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Austin Hangouts items and pinging IndexNow each run. ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Keep the live / news feed updated on cadence (2×/day) — on the site austinhangout.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Austin Hangouts items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Austin Hangouts: 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 Hangouts 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. | ||||
| 23 | 57 | Design | 2026-07-19 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site austinhangout.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 | 51 | SEO | 2026-07-23 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site austinhangout.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 | 50 | SEO | 2026-07-24 | on austinhangout.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Add Article + FAQ structured data — on the site austinhangout.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 | 49 | SEO | 2026-07-24 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site austinhangout.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 | 45 | Video | 2026-07-27 | on austinhangout.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Hangouts videos. Re-verify embeds. ★ Copy-paste prompt for austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site austinhangout.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Hangouts videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Austin Hangouts videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 39 | Monetize | 2026-07-31 | on austinhangout.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 austinhangout.com You are working on ONE specific website: austinhangout.com (live at https://austinhangout.com/), a Austin Hangouts site in the WholeTech network, served from /var/www/austinhangout.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinhangout.com and no other site — make all changes on austinhangout.com. Act like a senior editor and web engineer who knows the Austin Hangouts niche cold. GOAL (on austinhangout.com) Verify affiliate links and ad placement resolve correctly — on the site austinhangout.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. | ||||