A prioritized, living to-do list for austintechnews.live, built from this site's sources and current trends in Austin Tech. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Flagship | 2026-06-19 | on austintechnews.live Build the definitive Austin Tech cornerstone guide |
Create the single most useful, authoritative page on Austin Tech 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Build the definitive Austin Tech cornerstone guide — on the site austintechnews.live. WHY IT MATTERS Create the single most useful, authoritative page on Austin Tech 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 Tech — 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 Tech resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 2 | 97 | Security | 2026-06-21 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austintechnews.live. 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 | 96 | Security | 2026-06-21 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Lock down sensitive data — nothing private is publicly reachable — on the site austintechnews.live. WHY IT MATTERS Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 4 | 94 | Flagship | 2026-06-23 | on austintechnews.live Add an interactive tool and an email capture for Austin Tech |
Build one genuinely useful interactive element for Austin Tech (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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Add an interactive tool and an email capture for Austin Tech — on the site austintechnews.live. WHY IT MATTERS Build one genuinely useful interactive element for Austin Tech (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 Tech — 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 Tech resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 5 | 94 | Security | 2026-06-23 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Verify HTTPS, security headers & a safe Agents-First surface — on the site austintechnews.live. WHY IT MATTERS Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 91 | Flagship | 2026-06-25 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austintechnews.live. 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 Tech — 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 Tech 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 | 90 | Popularity | 2026-06-26 | on austintechnews.live Daily short Austin tech news posts |
Publish two or three terse daily items on Austin tech, funding, moves, launches, sourced and linked to announcements, generated through the /root/gen-live.py mass-content engine with human-checked headlines. The .live TLD promises freshness; daily cadence is the whole brand. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Daily short Austin tech news posts — on the site austintechnews.live. WHY IT MATTERS Publish two or three terse daily items on Austin tech, funding, moves, launches, sourced and linked to announcements, generated through the /root/gen-live.py mass-content engine with human-checked headlines. The .live TLD promises freshness; daily cadence is the whole brand. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 8 | 90 | Trends | 2026-06-26 | on austintechnews.live Publish: The Austin funding rounds and hires worth tracking |
Trending angle in Austin Tech. 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Publish: The Austin funding rounds and hires worth tracking — on the site austintechnews.live. WHY IT MATTERS Trending angle in Austin Tech. 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 Tech 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 | 85 | Popularity | 2026-06-29 | on austintechnews.live Running Austin funding-round tracker page |
Maintain one permanent page logging every announced Austin startup raise, company, amount, stage, lead investor, date, citing each public announcement. A cumulative, sourced tracker becomes the reference local journalists and VCs check monthly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Running Austin funding-round tracker page — on the site austintechnews.live. WHY IT MATTERS Maintain one permanent page logging every announced Austin startup raise, company, amount, stage, lead investor, date, citing each public announcement. A cumulative, sourced tracker becomes the reference local journalists and VCs check monthly. (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 | 84 | Trends | 2026-06-30 | on austintechnews.live Publish: The move-to-Austin tech migration data |
Trending angle in Austin Tech. 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Publish: The move-to-Austin tech migration data — on the site austintechnews.live. WHY IT MATTERS Trending angle in Austin Tech. 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 Tech reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 83 | Popularity | 2026-06-30 | on austintechnews.live Embed Austin tech talk videos |
Add a /videos/ section embedding real conference talks and keynotes from Austin tech events, verifying every ID with check-embed.mjs and dropping non-embeddable entries. Talk pages capture speaker-name and company searches that news posts alone miss. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Embed Austin tech talk videos — on the site austintechnews.live. WHY IT MATTERS Add a /videos/ section embedding real conference talks and keynotes from Austin tech events, verifying every ID with check-embed.mjs and dropping non-embeddable entries. Talk pages capture speaker-name and company searches that news posts alone miss. (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 | 83 | Trends | 2026-06-30 | on austintechnews.live Publish: Which startups are hiring right now |
Trending angle in Austin Tech. 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Publish: Which startups are hiring right now — on the site austintechnews.live. WHY IT MATTERS Trending angle in Austin Tech. 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 Tech reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 77 | Revenue | 2026-07-05 | on austintechnews.live Newsletter with future labeled sponsor slot |
Embed the wholetech.com/newsletter/widget.js signup on every article for a daily-brief list, and once the list matures, sell one clearly labeled sponsor line per issue to a local tech firm or recruiter. Owned distribution is the durable news-site asset. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Newsletter with future labeled sponsor slot — on the site austintechnews.live. WHY IT MATTERS Embed the wholetech.com/newsletter/widget.js signup on every article for a daily-brief list, and once the list matures, sell one clearly labeled sponsor line per issue to a local tech firm or recruiter. Owned distribution is the durable news-site 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. | ||||
| 14 | 76 | Revenue | 2026-07-05 | on austintechnews.live AdSense across daily news inventory |
Run shared AdSense pub-7759195213529699 on article and archive templates, where a daily-publishing site generates real page-view inventory. News layouts absorb standard placements gracefully, so this becomes the domain's monetization baseline. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) AdSense across daily news inventory — on the site austintechnews.live. WHY IT MATTERS Run shared AdSense pub-7759195213529699 on article and archive templates, where a daily-publishing site generates real page-view inventory. News layouts absorb standard placements gracefully, so this becomes the domain's monetization baseline. (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 | 76 | Trends | 2026-07-05 | on austintechnews.live Publish: Events and demo days coming up |
Trending angle in Austin Tech. 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Publish: Events and demo days coming up — on the site austintechnews.live. WHY IT MATTERS Trending angle in Austin Tech. 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 Tech 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. | ||||
| 16 | 72 | Content | 2026-07-08 | on austintechnews.live Deepen the main Austin Tech 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Deepen the main Austin Tech guide with current data and examples — on the site austintechnews.live. 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 Tech 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 Tech. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 17 | 71 | Design | 2026-07-09 | on austintechnews.live Wire-service terminal with timestamped dateline slugs |
Art-direct like a newswire terminal: dense headline stack, monospace timestamps, AUSTIN dateline slugs opening each item, electric-blue LIVE indicator pulsing in the header on dark ground. The Bloomberg-terminal urgency matches the .live promise visually. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Wire-service terminal with timestamped dateline slugs — on the site austintechnews.live. WHY IT MATTERS Art-direct like a newswire terminal: dense headline stack, monospace timestamps, AUSTIN dateline slugs opening each item, electric-blue LIVE indicator pulsing in the header on dark ground. The Bloomberg-terminal urgency matches the .live promise visually. (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 | 70 | Revenue | 2026-07-10 | on austintechnews.live Austin tech reading roundups with Amazon tag |
Publish occasional roundups of books by or about Austin tech figures and the city's startup history, tagged colinfirthfan-20. Weekend-read features vary the daily cadence, satisfy deeper-dive readers, and monetize without touching news integrity. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Austin tech reading roundups with Amazon tag — on the site austintechnews.live. WHY IT MATTERS Publish occasional roundups of books by or about Austin tech figures and the city's startup history, tagged colinfirthfan-20. Weekend-read features vary the daily cadence, satisfy deeper-dive readers, and monetize without touching news integrity. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 19 | 68 | Content | 2026-07-11 | on austintechnews.live Add an FAQ answering the top questions in Austin Tech |
Pull the real questions people ask in Austin Tech and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Add an FAQ answering the top questions in Austin Tech — on the site austintechnews.live. WHY IT MATTERS Pull the real questions people ask in Austin Tech and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Austin Tech 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 Tech. - 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. | ||||
| 20 | 68 | Design | 2026-07-11 | on austintechnews.live Source chips and ticker strip on stories |
Give every story card a small source chip naming the cited outlet or company and run a slim scrolling ticker of the day's headlines across the top. Wire-room furniture reinforces that items are sourced aggregation, building credibility into the layout itself. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Source chips and ticker strip on stories — on the site austintechnews.live. WHY IT MATTERS Give every story card a small source chip naming the cited outlet or company and run a slim scrolling ticker of the day's headlines across the top. Wire-room furniture reinforces that items are sourced aggregation, building credibility into the layout itself. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 67 | AEO | 2026-07-12 | on austintechnews.live NewsArticle schema and per-publish IndexNow pings |
Mark every item with NewsArticle schema including datePublished and cited source, and ping IndexNow from the webroot key on each publish, because freshness recall is everything for a news domain. Keep both sitemaps regenerating with the daily cron. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) NewsArticle schema and per-publish IndexNow pings — on the site austintechnews.live. WHY IT MATTERS Mark every item with NewsArticle schema including datePublished and cited source, and ping IndexNow from the webroot key on each publish, because freshness recall is everything for a news domain. Keep both sitemaps regenerating with the daily cron. (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 | 60 | Design | 2026-07-17 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Apply a WT-Skins kit to lift the design and Agents-First score — on the site austintechnews.live. 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 | 60 | Product | 2026-07-17 | on austintechnews.live Sortable Austin tech company directory |
Build an alldomains-style sortable table of Austin tech companies: sector, headquarters neighborhood, founded year, headcount band from public sources, linked to their coverage archive on the site. The directory converts drive-by news readers into reference users. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Sortable Austin tech company directory — on the site austintechnews.live. WHY IT MATTERS Build an alldomains-style sortable table of Austin tech companies: sector, headquarters neighborhood, founded year, headcount band from public sources, linked to their coverage archive on the site. The directory converts drive-by news readers into reference 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. | ||||
| 24 | 57 | SEO | 2026-07-19 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Submit updated URLs via IndexNow and refresh the sitemap — on the site austintechnews.live. 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 | 54 | Fresh | 2026-07-21 | on austintechnews.live Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Austin Tech items and pinging IndexNow each run. ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Keep the live / news feed updated on cadence (2×/day) — on the site austintechnews.live. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Austin Tech items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Austin Tech: 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 Tech 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. | ||||
| 26 | 46 | SEO | 2026-07-26 | on austintechnews.live Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Add Article + FAQ structured data — on the site austintechnews.live. WHY IT MATTERS Schema.org markup earns richer results and helps answer-engines cite the page correctly. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 27 | 45 | SEO | 2026-07-27 | on austintechnews.live 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 austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Strengthen internal links between the core, /sources/ and this worksheet — on the site austintechnews.live. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 44 | Video | 2026-07-28 | on austintechnews.live Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Tech videos. Re-verify embeds. ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Refresh the /videos/ playlist with current, embeddable uploads — on the site austintechnews.live. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Austin Tech videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Austin Tech videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 29 | 42 | Monetize | 2026-07-29 | on austintechnews.live Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for austintechnews.live You are working on ONE specific website: austintechnews.live (live at https://austintechnews.live/), a Austin Tech site in the WholeTech network, served from /var/www/austintechnews.live/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechnews.live and no other site — make all changes on austintechnews.live. Act like a senior editor and web engineer who knows the Austin Tech niche cold. GOAL (on austintechnews.live) Add the network affiliate + AdSense setup — on the site austintechnews.live. WHY IT MATTERS Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||