What to do next on this site

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Lock down sensitive data — nothing private is publicly reachable — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Build the definitive Startup Tech cornerstone guide — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Publish: A current, data-backed explainer in Startup Tech — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Add an interactive tool and an email capture for Startup Tech — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Quarterly Austin startup trend reports from public data — on the site atxtechtrends.com.

WHY IT MATTERS
Compile quarterly analyses — sectors raising, hiring signals from public job-board counts, office-footprint moves — built exclusively from announced, linkable sources with a methodology note. Analysts and newsletter writers cite structured trend reports; that citation loop is this domain's entire popularity engine. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Trend-line explainers connecting three data points — on the site atxtechtrends.com.

WHY IT MATTERS
Own the connective genre: pieces linking verified events into a trend claim — three semiconductor announcements make a corridor story — with every input cited. This analysis layer is what the cluster's news sites cannot do at speed, and it earns the longest content half-life. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Publish: The question your Startup Tech audience is searching most right now — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Rank Austin's startup sectors with transparent criteria — on the site atxtechtrends.com.

WHY IT MATTERS
Publish a living Austin tech sector index — AI, semiconductors, CPG-tech, space — ranked by countable public signals (announced raises, headcount postings) with the formula shown. Transparent-methodology rankings draw both links and productive argument, and updating quarterly renews the story each cycle. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Publish: A 'what changed in 2026' round-up for Startup Tech — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
AdSense against analyst-intent traffic — on the site atxtechtrends.com.

WHY IT MATTERS
Run pub-7759195213529699 on reports and rankings; readers researching market trends attract high-value B2B advertisers relative to general news traffic. Long-form analysis pages support two units without crowding, and the quarterly cadence keeps the archive growing predictably. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Deepen the main Startup Tech guide with current data and examples — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Amazon shelf of startup and market books — on the site atxtechtrends.com.

WHY IT MATTERS
Attach a disclosed colinfirthfan-20 reading list to each report — books on the sector analyzed, Austin business history, market-analysis classics — with one honest line on relevance each. Business readers buy books; a per-report shelf converts contextually without cheapening the analysis. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Newsletter positioned as the quarterly brief — on the site atxtechtrends.com.

WHY IT MATTERS
Embed wholetech.com/newsletter/widget.js pitching the trend report delivered as an email brief the day it publishes. Analyst-flavored lists carry the highest per-subscriber sponsorship value in local media; grow it honestly and describe it to future sponsors only from real counts. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Chart-first aesthetic: sparklines, annotated trend lines — on the site atxtechtrends.com.

WHY IT MATTERS
Art-direct as a data publication: every report opens with a hero chart, headline claims carry inline sparklines, and annotated trend-line callouts (flat serif labels on thin leader lines) mark the three data points behind each claim. The visual language is the argument made visible. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Quarterly-report print aesthetic for the archives — on the site atxtechtrends.com.

WHY IT MATTERS
Style report pages like a printed market brief — cover-block with quarter designation, two-column body at reading width, figure numbering, and a document-footer folio. The institutional-report look reinforces the byline policy and makes screenshots of any page instantly attributable. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Add an FAQ answering the top questions in Startup Tech — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Public methodology page as the trust anchor — on the site atxtechtrends.com.

WHY IT MATTERS
Publish a permanent page documenting exactly which public sources feed the rankings, how signals are counted, and what the site will never do (no estimates presented as fact, no unnamed sourcing). In an analysis niche, auditable methodology is the product differentiator — and it compounds citations. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Dataset and Article schema on every report — on the site atxtechtrends.com.

WHY IT MATTERS
Mark reports with Article JSON-LD and expose underlying tables with Dataset markup plus downloadable CSV. Answer engines increasingly cite structured local data sources directly; being the machine-readable source for Austin startup trends is a defensible AEO moat. Verify 90-plus on af-deploy.py. (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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Keep the live / news feed updated on cadence (2×/day) — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Add Article + FAQ structured data — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site atxtechtrends.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.

You are working on ONE specific website: atxtechtrends.com (live at https://atxtechtrends.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxtechtrends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxtechtrends.com and no other site — make all changes on atxtechtrends.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold.

GOAL (on atxtechtrends.com)
Add the network affiliate + AdSense setup — on the site atxtechtrends.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.