A prioritized, living to-do list for austintechtrends.com, built from this site's sources and current trends in Startup 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 | Security | 2026-06-19 | on austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Lock down sensitive data — nothing private is publicly reachable — on the site austintechtrends.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 | 98 | Security | 2026-06-20 | on austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austintechtrends.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 austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site austintechtrends.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 | 95 | Flagship | 2026-06-22 | on austintechtrends.com Build the definitive Startup Tech cornerstone guide |
Create the single most useful, authoritative page on Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Build the definitive Startup Tech cornerstone guide — on the site austintechtrends.com. WHY IT MATTERS Create the single most useful, authoritative page on Startup 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 Startup 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 Startup 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 | 95 | Flagship | 2026-06-22 | on austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austintechtrends.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 Startup 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 Startup 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. | ||||
| 6 | 92 | Flagship | 2026-06-24 | on austintechtrends.com Add an interactive tool and an email capture for Startup Tech |
Build one genuinely useful interactive element for Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Add an interactive tool and an email capture for Startup Tech — on the site austintechtrends.com. WHY IT MATTERS Build one genuinely useful interactive element for Startup 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 Startup 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 Startup 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 | Trends | 2026-06-26 | on austintechtrends.com Publish: A current, data-backed explainer in Startup Tech |
Trending angle in Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Publish: A current, data-backed explainer in Startup Tech — on the site austintechtrends.com. WHY IT MATTERS Trending angle in Startup 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 Startup 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. | ||||
| 8 | 88 | Popularity | 2026-06-27 | on austintechtrends.com Quarterly Austin startup trends analysis reports |
Publish a substantial quarterly analysis synthesizing cited public data, CBRE tech-talent reports, Opportunity Austin figures, announced raises, into named trends with a permanent URL per quarter. Dated analytical reports get cited by decks and journalists, unlike daily churn. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Quarterly Austin startup trends analysis reports — on the site austintechtrends.com. WHY IT MATTERS Publish a substantial quarterly analysis synthesizing cited public data, CBRE tech-talent reports, Opportunity Austin figures, announced raises, into named trends with a permanent URL per quarter. Dated analytical reports get cited by decks and journalists, unlike daily churn. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 9 | 85 | Popularity | 2026-06-29 | on austintechtrends.com Austin startup ecosystem map pages |
Build one page per ecosystem layer, accelerators, VC firms, major coworking hubs, university programs, with real entries, official links, and short profiles. Cross-link the Capital Factory material on texascoworking.com for depth. Ecosystem maps are evergreen link magnets for founders. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Austin startup ecosystem map pages — on the site austintechtrends.com. WHY IT MATTERS Build one page per ecosystem layer, accelerators, VC firms, major coworking hubs, university programs, with real entries, official links, and short profiles. Cross-link the Capital Factory material on texascoworking.com for depth. Ecosystem maps are evergreen link magnets for founders. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 85 | Trends | 2026-06-29 | on austintechtrends.com Publish: The question your Startup Tech audience is searching most right now |
Trending angle in Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Publish: The question your Startup Tech audience is searching most right now — on the site austintechtrends.com. WHY IT MATTERS Trending angle in Startup 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 Startup 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 | 85 | Trends | 2026-06-29 | on austintechtrends.com Publish: A 'what changed in 2026' round-up for Startup Tech |
Trending angle in Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Publish: A 'what changed in 2026' round-up for Startup Tech — on the site austintechtrends.com. WHY IT MATTERS Trending angle in Startup 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 Startup 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. | ||||
| 12 | 84 | Popularity | 2026-06-30 | on austintechtrends.com Founder interview series with fixed questions |
Run an email-interview series asking Austin founders five fixed questions about building here, talent, capital, why Austin. Founders share their own features, and the accumulating answers become a citable longitudinal dataset about the ecosystem's mood. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Founder interview series with fixed questions — on the site austintechtrends.com. WHY IT MATTERS Run an email-interview series asking Austin founders five fixed questions about building here, talent, capital, why Austin. Founders share their own features, and the accumulating answers become a citable longitudinal dataset about the ecosystem's mood. (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 | 79 | Revenue | 2026-07-03 | on austintechtrends.com Labeled sponsorship on quarterly reports |
Offer one clearly marked presenting-sponsor slot per quarterly trends report to a Austin-relevant service firm, bank, law firm, recruiter, flat rate, zero editorial influence, disclosure at top. Inquiry form drafts a Gmail notification only, never auto-sends. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Labeled sponsorship on quarterly reports — on the site austintechtrends.com. WHY IT MATTERS Offer one clearly marked presenting-sponsor slot per quarterly trends report to a Austin-relevant service firm, bank, law firm, recruiter, flat rate, zero editorial influence, disclosure at top. Inquiry form drafts a Gmail notification only, never auto-sends. (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 austintechtrends.com Startup bookshelf pages with Amazon tag |
Curate reading lists matched to the trend reports, respected titles on scaling, fundraising, and company-building referenced in analysis pieces, tagged colinfirthfan-20. Contextual bookshelf links inside analytical content convert better than standalone listicles. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Startup bookshelf pages with Amazon tag — on the site austintechtrends.com. WHY IT MATTERS Curate reading lists matched to the trend reports, respected titles on scaling, fundraising, and company-building referenced in analysis pieces, tagged colinfirthfan-20. Contextual bookshelf links inside analytical content convert better than standalone listicles. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 15 | 74 | Revenue | 2026-07-07 | on austintechtrends.com AdSense on ecosystem and archive pages |
Run shared AdSense pub-7759195213529699 on ecosystem map and report-archive templates where research dwell is long, keeping the current quarter's flagship report cleaner so its sponsor placement stays exclusive and visibly premium. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) AdSense on ecosystem and archive pages — on the site austintechtrends.com. WHY IT MATTERS Run shared AdSense pub-7759195213529699 on ecosystem map and report-archive templates where research dwell is long, keeping the current quarter's flagship report cleaner so its sponsor placement stays exclusive and visibly premium. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 16 | 71 | Content | 2026-07-09 | on austintechtrends.com Deepen the main Startup 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Deepen the main Startup Tech guide with current data and examples — on the site austintechtrends.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 Startup 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 Startup 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 | 70 | Design | 2026-07-10 | on austintechtrends.com VC-memo typography with rising trend-line motifs |
Art-direct like a sharp investment memo: confident serif headlines over white, violet accent ink, section dividers drawn as rising trend lines, and the Austin skyline abstracted into a bar-chart silhouette for the masthead. Analytical authority, not tech-blog gradient soup. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) VC-memo typography with rising trend-line motifs — on the site austintechtrends.com. WHY IT MATTERS Art-direct like a sharp investment memo: confident serif headlines over white, violet accent ink, section dividers drawn as rising trend lines, and the Austin skyline abstracted into a bar-chart silhouette for the masthead. Analytical authority, not tech-blog gradient soup. (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 | 69 | Design | 2026-07-10 | on austintechtrends.com Data callouts as annotated chart cards |
Present every cited statistic in a consistent annotated chart-card style, figure, source, date stamp, one-line takeaway, using only real sourced numbers. A disciplined data-card system makes reports screenshotable, and those screenshots carry the brand into decks. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Data callouts as annotated chart cards — on the site austintechtrends.com. WHY IT MATTERS Present every cited statistic in a consistent annotated chart-card style, figure, source, date stamp, one-line takeaway, using only real sourced numbers. A disciplined data-card system makes reports screenshotable, and those screenshots carry the brand into decks. (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 | AEO | 2026-07-12 | on austintechtrends.com Cited FAQs on Austin startup ecosystem |
Add FAQ schema answering which VCs invest in Austin, what accelerators exist, and how the ecosystem is trending, each answer citing the current quarterly report with its date. Run /root/af-deploy.py toward 90+ and keep both sitemaps plus IndexNow active. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Cited FAQs on Austin startup ecosystem — on the site austintechtrends.com. WHY IT MATTERS Add FAQ schema answering which VCs invest in Austin, what accelerators exist, and how the ecosystem is trending, each answer citing the current quarterly report with its date. Run /root/af-deploy.py toward 90+ and keep both sitemaps plus IndexNow active. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 65 | Content | 2026-07-13 | on austintechtrends.com Add an FAQ answering the top questions in Startup Tech |
Pull the real questions people ask in Startup Tech and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Add an FAQ answering the top questions in Startup Tech — on the site austintechtrends.com. WHY IT MATTERS Pull the real questions people ask in Startup Tech and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Startup 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 Startup 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. | ||||
| 21 | 59 | Product | 2026-07-17 | on austintechtrends.com Sortable accelerator and VC worksheet |
Build an alldomains-style sortable table of Austin accelerators and funds: focus, stage, check size where published, notable portfolio, application link. Founders return to comparison tables repeatedly during a raise, making this the domain's habitual-use page. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Sortable accelerator and VC worksheet — on the site austintechtrends.com. WHY IT MATTERS Build an alldomains-style sortable table of Austin accelerators and funds: focus, stage, check size where published, notable portfolio, application link. Founders return to comparison tables repeatedly during a raise, making this the domain's habitual-use page. (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 | 58 | Fresh | 2026-07-18 | on austintechtrends.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Startup Tech items and pinging IndexNow each run. ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Keep the live / news feed updated on cadence (2×/day) — on the site austintechtrends.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Startup Tech items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Startup 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 Startup 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. | ||||
| 23 | 53 | SEO | 2026-07-21 | on austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site austintechtrends.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. | ||||
| 24 | 49 | SEO | 2026-07-24 | on austintechtrends.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Add Article + FAQ structured data — on the site austintechtrends.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. | ||||
| 25 | 49 | SEO | 2026-07-24 | on austintechtrends.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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site austintechtrends.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. | ||||
| 26 | 43 | Design | 2026-07-28 | on austintechtrends.com Audit against the Agents-First scorer (target 90+) |
Run the live AF scorer; close any gaps in clarity, links and machine-readability. ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Audit against the Agents-First scorer (target 90+) — on the site austintechtrends.com. WHY IT MATTERS Run the live AF scorer; close any gaps in clarity, links and machine-readability. 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. | ||||
| 27 | 43 | Video | 2026-07-28 | on austintechtrends.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Startup Tech videos. Re-verify embeds. ★ Copy-paste prompt for austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site austintechtrends.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Startup Tech videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Startup 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. | ||||
| 28 | 41 | Monetize | 2026-07-30 | on austintechtrends.com 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 austintechtrends.com You are working on ONE specific website: austintechtrends.com (live at https://austintechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/austintechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austintechtrends.com and no other site — make all changes on austintechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on austintechtrends.com) Add the network affiliate + AdSense setup — on the site austintechtrends.com. 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. | ||||