A prioritized, living to-do list for aiaustintexas.com, built from this site's sources and current trends in Artificial Intelligence. 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 aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Lock down sensitive data — nothing private is publicly reachable — on the site aiaustintexas.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 | 96 | Security | 2026-06-21 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site aiaustintexas.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 | 96 | Security | 2026-06-21 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site aiaustintexas.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. | ||||
| 4 | 94 | Flagship | 2026-06-23 | on aiaustintexas.com Build the definitive Artificial Intelligence cornerstone guide |
Create the single most useful, authoritative page on Artificial Intelligence 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Build the definitive Artificial Intelligence cornerstone guide — on the site aiaustintexas.com. WHY IT MATTERS Create the single most useful, authoritative page on Artificial Intelligence 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 Artificial Intelligence — 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 Artificial Intelligence 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 | 93 | Flagship | 2026-06-23 | on aiaustintexas.com Add an interactive tool and an email capture for Artificial Intelligence |
Build one genuinely useful interactive element for Artificial Intelligence (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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Add an interactive tool and an email capture for Artificial Intelligence — on the site aiaustintexas.com. WHY IT MATTERS Build one genuinely useful interactive element for Artificial Intelligence (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 Artificial Intelligence — 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 Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 91 | Flagship | 2026-06-25 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site aiaustintexas.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 Artificial Intelligence — 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 Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 91 | Popularity | 2026-06-25 | on aiaustintexas.com Austin AI events calendar, maintained weekly |
Build the definitive Austin AI events page — meetups, Capital Factory sessions, university talks — as a sortable worksheet-style table updated weekly, listing only verifiable public events. Local event queries are high-intent and poorly served; a reliably fresh calendar becomes the page Austin AI people bookmark and share. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Austin AI events calendar, maintained weekly — on the site aiaustintexas.com. WHY IT MATTERS Build the definitive Austin AI events page — meetups, Capital Factory sessions, university talks — as a sortable worksheet-style table updated weekly, listing only verifiable public events. Local event queries are high-intent and poorly served; a reliably fresh calendar becomes the page Austin AI people bookmark and share. (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 | 91 | Trends | 2026-06-25 | on aiaustintexas.com Publish: The latest frontier AI model tier and what it unlocks |
Trending angle in Artificial Intelligence. 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Publish: The latest frontier AI model tier and what it unlocks — on the site aiaustintexas.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 9 | 88 | Trends | 2026-06-27 | on aiaustintexas.com Publish: Agentic workflows a small business can deploy this month |
Trending angle in Artificial Intelligence. 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Publish: Agentic workflows a small business can deploy this month — on the site aiaustintexas.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence 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 | 87 | Popularity | 2026-06-28 | on aiaustintexas.com Directory of Austin AI companies as worksheet |
Publish a sortable directory of Austin-area AI companies and labs — name, focus, neighborhood, careers link — using the alldomains worksheet pattern. Populate only from public information. Directories earn links from every company listed and rank for austin ai companies, the head query in this niche. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Directory of Austin AI companies as worksheet — on the site aiaustintexas.com. WHY IT MATTERS Publish a sortable directory of Austin-area AI companies and labs — name, focus, neighborhood, careers link — using the alldomains worksheet pattern. Populate only from public information. Directories earn links from every company listed and rank for austin ai companies, the head query in this niche. (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 | 85 | Trends | 2026-06-29 | on aiaustintexas.com Publish: Answer-engine optimization — getting cited by AI search |
Trending angle in Artificial Intelligence. 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Publish: Answer-engine optimization — getting cited by AI search — on the site aiaustintexas.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence 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. | ||||
| 12 | 82 | Popularity | 2026-07-01 | on aiaustintexas.com Neighborhood guide: where Austin AI actually clusters |
Write a grounded guide to Austin's AI geography — downtown around Capital Factory, the Domain, East Austin studios — with what actually happens where. Relocating engineers and visiting founders search exactly this; it differentiates from national AI news sites that cannot write street-level Austin. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Neighborhood guide: where Austin AI actually clusters — on the site aiaustintexas.com. WHY IT MATTERS Write a grounded guide to Austin's AI geography — downtown around Capital Factory, the Domain, East Austin studios — with what actually happens where. Relocating engineers and visiting founders search exactly this; it differentiates from national AI news sites that cannot write street-level Austin. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 80 | Trends | 2026-07-03 | on aiaustintexas.com Publish: Practical AI guardrails and what to avoid |
Trending angle in Artificial Intelligence. 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Publish: Practical AI guardrails and what to avoid — on the site aiaustintexas.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 14 | 78 | Revenue | 2026-07-04 | on aiaustintexas.com Travala block for SXSW and conference travel |
Add the live Impact Travala integration on event and visiting-Austin pages — hotel booking for SXSW, AI conference weekends. Event-page readers are trip planners by definition; the crypto-pay travel angle even fits the tech audience. The integration already runs on 18 network sites to copy. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Travala block for SXSW and conference travel — on the site aiaustintexas.com. WHY IT MATTERS Add the live Impact Travala integration on event and visiting-Austin pages — hotel booking for SXSW, AI conference weekends. Event-page readers are trip planners by definition; the crypto-pay travel angle even fits the tech audience. The integration already runs on 18 network sites to copy. (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 | 75 | Content | 2026-07-06 | on aiaustintexas.com Deepen the main Artificial Intelligence 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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Deepen the main Artificial Intelligence guide with current data and examples — on the site aiaustintexas.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 Artificial Intelligence 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 Artificial Intelligence. - 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 | 74 | Revenue | 2026-07-07 | on aiaustintexas.com TicketNetwork on Austin event content |
Where the calendar covers ticketed Austin happenings — festivals, arena shows conference visitors bolt on — include the TicketNetwork block. Visitors planning an Austin tech trip buy entertainment around it; this monetizes the travel-planning session honestly without touching free community meetup listings. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) TicketNetwork on Austin event content — on the site aiaustintexas.com. WHY IT MATTERS Where the calendar covers ticketed Austin happenings — festivals, arena shows conference visitors bolt on — include the TicketNetwork block. Visitors planning an Austin tech trip buy entertainment around it; this monetizes the travel-planning session honestly without touching free community meetup listings. (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 | 74 | Revenue | 2026-07-07 | on aiaustintexas.com Sponsor slot for one Austin company, clearly labeled |
Offer a single clearly-labeled supported-by slot on the calendar page to one local AI company per quarter, with inquiries via a form that writes a Gmail DRAFT to Paul. One honest sponsor beats banner clutter, and the directory gives you the prospect list. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Sponsor slot for one Austin company, clearly labeled — on the site aiaustintexas.com. WHY IT MATTERS Offer a single clearly-labeled supported-by slot on the calendar page to one local AI company per quarter, with inquiries via a form that writes a Gmail DRAFT to Paul. One honest sponsor beats banner clutter, and the directory gives you the prospect list. (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. | ||||
| 18 | 71 | Design | 2026-07-09 | on aiaustintexas.com Violet-crown palette, bat-bridge silhouette, limestone texture |
Art-direct Austin-specific: the violet-crown sunset gradient as the header, a Congress Bridge bats silhouette motif in section transitions, warm limestone texture panels, and circuit-trace linework connecting them. It should read as unmistakably Austin-plus-AI, not a generic tech-blue template. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Violet-crown palette, bat-bridge silhouette, limestone texture — on the site aiaustintexas.com. WHY IT MATTERS Art-direct Austin-specific: the violet-crown sunset gradient as the header, a Congress Bridge bats silhouette motif in section transitions, warm limestone texture panels, and circuit-trace linework connecting them. It should read as unmistakably Austin-plus-AI, not a generic tech-blue template. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 19 | 67 | Content | 2026-07-12 | on aiaustintexas.com Add an FAQ answering the top questions in Artificial Intelligence |
Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Add an FAQ answering the top questions in Artificial Intelligence — on the site aiaustintexas.com. WHY IT MATTERS Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Artificial Intelligence 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 Artificial Intelligence. - 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 | 64 | Design | 2026-07-14 | on aiaustintexas.com Event cards styled as show posters |
Render calendar entries as mini gig-poster cards — bold condensed type, date block treatment borrowed from Austin's live-music poster tradition. It ties the tech calendar to the city's visual heritage and makes individual event cards screenshot-worthy for organizers to reshare. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Event cards styled as show posters — on the site aiaustintexas.com. WHY IT MATTERS Render calendar entries as mini gig-poster cards — bold condensed type, date block treatment borrowed from Austin's live-music poster tradition. It ties the tech calendar to the city's visual heritage and makes individual event cards screenshot-worthy for organizers to reshare. (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 | 62 | AEO | 2026-07-15 | on aiaustintexas.com Event schema on every calendar entry |
Mark each listing with Event JSON-LD — name, date, venue, organizer from public sources — plus FAQ schema for what AI meetups are in Austin. Two sitemaps, IndexNow ping on weekly updates, af-deploy.py to 90+. Agents asked about Austin AI events should pull this feed. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Event schema on every calendar entry — on the site aiaustintexas.com. WHY IT MATTERS Mark each listing with Event JSON-LD — name, date, venue, organizer from public sources — plus FAQ schema for what AI meetups are in Austin. Two sitemaps, IndexNow ping on weekly updates, af-deploy.py to 90+. Agents asked about Austin AI events should pull this feed. (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 | Popularity | 2026-07-17 | on aiaustintexas.com Monthly Austin AI digest via newsletter widget |
Wire wholetech.com/newsletter/widget.js promising a monthly digest: next month's events plus new directory entries. Local scenes run on email; a modest, reliable digest makes this site the connective tissue of Austin AI and compounds return visits regardless of algorithm shifts. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Monthly Austin AI digest via newsletter widget — on the site aiaustintexas.com. WHY IT MATTERS Wire wholetech.com/newsletter/widget.js promising a monthly digest: next month's events plus new directory entries. Local scenes run on email; a modest, reliable digest makes this site the connective tissue of Austin AI and compounds return visits regardless of algorithm shifts. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 23 | 56 | Design | 2026-07-19 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site aiaustintexas.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 | 56 | Fresh | 2026-07-19 | on aiaustintexas.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Keep the live / news feed updated on cadence (2×/day) — on the site aiaustintexas.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Artificial Intelligence: 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 Artificial Intelligence items on schedule and is discovered quickly. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 52 | SEO | 2026-07-22 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site aiaustintexas.com. WHY IT MATTERS Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 26 | 52 | SEO | 2026-07-22 | on aiaustintexas.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Add Article + FAQ structured data — on the site aiaustintexas.com. WHY IT MATTERS Schema.org markup earns richer results and helps answer-engines cite the page correctly. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 27 | 48 | SEO | 2026-07-25 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site aiaustintexas.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. | ||||
| 28 | 45 | Monetize | 2026-07-27 | on aiaustintexas.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 aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Verify affiliate links and ad placement resolve correctly — on the site aiaustintexas.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. | ||||
| 29 | 41 | Video | 2026-07-30 | on aiaustintexas.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. ★ Copy-paste prompt for aiaustintexas.com You are working on ONE specific website: aiaustintexas.com (live at https://aiaustintexas.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/aiaustintexas.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for aiaustintexas.com and no other site — make all changes on aiaustintexas.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on aiaustintexas.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site aiaustintexas.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Artificial Intelligence 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. | ||||