A prioritized, living to-do list for austinpads.com, built from this site's sources and current trends in Real Estate. 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 austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Lock down sensitive data — nothing private is publicly reachable — on the site austinpads.com. WHY IT MATTERS Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 2 | 96 | Security | 2026-06-21 | on austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site austinpads.com. WHY IT MATTERS Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 3 | 95 | Flagship | 2026-06-22 | on austinpads.com Build the definitive Real Estate cornerstone guide |
Create the single most useful, authoritative page on Real Estate 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Build the definitive Real Estate cornerstone guide — on the site austinpads.com. WHY IT MATTERS Create the single most useful, authoritative page on Real Estate 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 Real Estate — 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 Real Estate resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 4 | 94 | Flagship | 2026-06-23 | on austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site austinpads.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 Real Estate — 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 Real Estate resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 5 | 94 | Security | 2026-06-23 | on austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site austinpads.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. | ||||
| 6 | 92 | Trends | 2026-06-24 | on austinpads.com Publish: Where mortgage rates are heading and what it means for buyers now |
Trending angle in Real Estate. 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Publish: Where mortgage rates are heading and what it means for buyers now — on the site austinpads.com. WHY IT MATTERS Trending angle in Real Estate. 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 Real Estate 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. | ||||
| 7 | 91 | Flagship | 2026-06-25 | on austinpads.com Add an interactive tool and an email capture for Real Estate |
Build one genuinely useful interactive element for Real Estate (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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Add an interactive tool and an email capture for Real Estate — on the site austinpads.com. WHY IT MATTERS Build one genuinely useful interactive element for Real Estate (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 Real Estate — 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 Real Estate 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. | ||||
| 8 | 85 | Popularity | 2026-06-29 | on austinpads.com Renter neighborhood guides with cited rent data |
Build renter-first guides per neighborhood, typical rents cited from published market reports with dates, transit access, noise reality, walkability. Renters churn yearly, so this content has permanent recurring demand that homebuyer sites ignore. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Renter neighborhood guides with cited rent data — on the site austinpads.com. WHY IT MATTERS Build renter-first guides per neighborhood, typical rents cited from published market reports with dates, transit access, noise reality, walkability. Renters churn yearly, so this content has permanent recurring demand that homebuyer sites ignore. (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 austinpads.com First-apartment-in-Austin content series |
Publish a step-by-step series for first-time Austin renters: application docs, deposit norms, electricity-provider choice in a deregulated market, TXU versus Austin Energy areas. Practical process content wins the searches every arriving renter makes in their first month. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) First-apartment-in-Austin content series — on the site austinpads.com. WHY IT MATTERS Publish a step-by-step series for first-time Austin renters: application docs, deposit norms, electricity-provider choice in a deregulated market, TXU versus Austin Energy areas. Practical process content wins the searches every arriving renter makes in their first month. (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 austinpads.com Publish: The local inventory shift — is it a buyer's or seller's market this quarter |
Trending angle in Real Estate. 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Publish: The local inventory shift — is it a buyer's or seller's market this quarter — on the site austinpads.com. WHY IT MATTERS Trending angle in Real Estate. 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 Real Estate 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 | 84 | Trends | 2026-06-30 | on austinpads.com Publish: First-time-buyer assistance & down-payment programs for 2026 |
Trending angle in Real Estate. 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Publish: First-time-buyer assistance & down-payment programs for 2026 — on the site austinpads.com. WHY IT MATTERS Trending angle in Real Estate. 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 Real Estate 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 | 83 | Popularity | 2026-06-30 | on austinpads.com Quarterly rent-trend roundups from public reports |
Each quarter, publish a short roundup of Austin rent movement citing published sources such as Zumper or Apartment List reports, linked and dated, never inventing figures. Steady dated coverage becomes the local reference other writers cite when rents shift. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Quarterly rent-trend roundups from public reports — on the site austinpads.com. WHY IT MATTERS Each quarter, publish a short roundup of Austin rent movement citing published sources such as Zumper or Apartment List reports, linked and dated, never inventing figures. Steady dated coverage becomes the local reference other writers cite when rents shift. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 80 | Revenue | 2026-07-03 | on austinpads.com Apartment-setup checklists with Amazon tag |
Create move-in checklists for typical Austin unit types, blackout curtains for west-facing summer windows, portable AC helpers, renter-safe mounting gear, tagged colinfirthfan-20. Pegging products to Austin heat and rental constraints keeps recommendations concrete. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Apartment-setup checklists with Amazon tag — on the site austinpads.com. WHY IT MATTERS Create move-in checklists for typical Austin unit types, blackout curtains for west-facing summer windows, portable AC helpers, renter-safe mounting gear, tagged colinfirthfan-20. Pegging products to Austin heat and rental constraints keeps recommendations concrete. (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 | 80 | Trends | 2026-07-03 | on austinpads.com Publish: How AI home-valuation tools are changing pricing |
Trending angle in Real Estate. 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Publish: How AI home-valuation tools are changing pricing — on the site austinpads.com. WHY IT MATTERS Trending angle in Real Estate. 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 Real Estate 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. | ||||
| 15 | 78 | Revenue | 2026-07-04 | on austinpads.com Locator-referral lead form, draft-only notifications |
Add a clearly labeled form connecting renters to a licensed Austin apartment locator, a free-to-renter service with real referral economics. Submissions create Gmail draft notifications for manual review and forwarding, never auto-sending. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Locator-referral lead form, draft-only notifications — on the site austinpads.com. WHY IT MATTERS Add a clearly labeled form connecting renters to a licensed Austin apartment locator, a free-to-renter service with real referral economics. Submissions create Gmail draft notifications for manual review and forwarding, never auto-sending. (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 | 73 | Content | 2026-07-07 | on austinpads.com Deepen the main Real Estate 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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Deepen the main Real Estate guide with current data and examples — on the site austinpads.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 Real Estate 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 Real Estate. - 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 | 73 | Revenue | 2026-07-07 | on austinpads.com AdSense on guide and trend templates |
Run shared AdSense pub-7759195213529699 units on neighborhood guides and rent-trend pages where research dwell time is long, keeping the locator form page ad-free so its single call to action converts cleanly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) AdSense on guide and trend templates — on the site austinpads.com. WHY IT MATTERS Run shared AdSense pub-7759195213529699 units on neighborhood guides and rent-trend pages where research dwell time is long, keeping the locator form page ad-free so its single call to action converts cleanly. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 18 | 69 | Design | 2026-07-10 | on austinpads.com Guide cards styled as door-hanger tags |
Render neighborhood guide cards as apartment door-hanger tags, rounded hole at top, bold unit-number typography, hanging at slight varied angles in the grid. A playful physical metaphor renters recognize makes the index memorable and screenshot-friendly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Guide cards styled as door-hanger tags — on the site austinpads.com. WHY IT MATTERS Render neighborhood guide cards as apartment door-hanger tags, rounded hole at top, bold unit-number typography, hanging at slight varied angles in the grid. A playful physical metaphor renters recognize makes the index memorable and screenshot-friendly. (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 | 68 | Design | 2026-07-11 | on austinpads.com Floor-plan linework and key-tag iconography |
Art-direct from the leasing office: faint 2D unit floor-plan linework as background texture, brass key-tag icons for categories, and leasing-flyer accent chips for beds-baths-price strips. The apartment-hunt vocabulary distinguishes it from for-sale siblings instantly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Floor-plan linework and key-tag iconography — on the site austinpads.com. WHY IT MATTERS Art-direct from the leasing office: faint 2D unit floor-plan linework as background texture, brass key-tag icons for categories, and leasing-flyer accent chips for beds-baths-price strips. The apartment-hunt vocabulary distinguishes it from for-sale siblings instantly. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 66 | AEO | 2026-07-12 | on austinpads.com Dated average-rent FAQs with schema |
Add FAQ schema per neighborhood answering average rent questions with cited, dated figures refreshed quarterly, so assistants can quote answers with confidence. Maintain /sitemap.xml plus /sitemap/index.html and ping IndexNow at each quarterly refresh. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Dated average-rent FAQs with schema — on the site austinpads.com. WHY IT MATTERS Add FAQ schema per neighborhood answering average rent questions with cited, dated figures refreshed quarterly, so assistants can quote answers with confidence. Maintain /sitemap.xml plus /sitemap/index.html and ping IndexNow at each quarterly refresh. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 66 | Content | 2026-07-12 | on austinpads.com Add an FAQ answering the top questions in Real Estate |
Pull the real questions people ask in Real Estate and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Add an FAQ answering the top questions in Real Estate — on the site austinpads.com. WHY IT MATTERS Pull the real questions people ask in Real Estate and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Real Estate 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 Real Estate. - 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. | ||||
| 22 | 60 | Product | 2026-07-17 | on austinpads.com Move-in cost calculator, static JavaScript |
Ship a client-side calculator totaling true Austin move-in cost: deposit, application and admin fees, first month, utility setup, renter's insurance estimate. No backend, no data stored. Renters share cost calculators in apartment-hunt group chats constantly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Move-in cost calculator, static JavaScript — on the site austinpads.com. WHY IT MATTERS Ship a client-side calculator totaling true Austin move-in cost: deposit, application and admin fees, first month, utility setup, renter's insurance estimate. No backend, no data stored. Renters share cost calculators in apartment-hunt group chats constantly. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 23 | 59 | Design | 2026-07-17 | on austinpads.com Apply a WT-Skins kit to lift the design and Agents-First score |
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site austinpads.com. WHY IT MATTERS The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s. HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 24 | 56 | Fresh | 2026-07-19 | on austinpads.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Real Estate items and pinging IndexNow each run. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Keep the live / news feed updated on cadence (2×/day) — on the site austinpads.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Real Estate items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Real Estate: 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 Real Estate items on schedule and is discovered quickly. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 51 | SEO | 2026-07-23 | on austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site austinpads.com. WHY IT MATTERS Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 26 | 48 | SEO | 2026-07-25 | on austinpads.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Add Article + FAQ structured data — on the site austinpads.com. WHY IT MATTERS Schema.org markup earns richer results and helps answer-engines cite the page correctly. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 27 | 46 | SEO | 2026-07-26 | on austinpads.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 austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site austinpads.com. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 41 | Video | 2026-07-30 | on austinpads.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Real Estate videos. Re-verify embeds. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site austinpads.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Real Estate videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Real Estate videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 29 | 39 | Monetize | 2026-07-31 | on austinpads.com Verify affiliate links and ad placement resolve correctly |
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. ★ Copy-paste prompt for austinpads.com You are working on ONE specific website: austinpads.com (live at https://austinpads.com/), a Real Estate site in the WholeTech network, served from /var/www/austinpads.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for austinpads.com and no other site — make all changes on austinpads.com. Act like a senior editor and web engineer who knows the Real Estate niche cold. GOAL (on austinpads.com) Verify affiliate links and ad placement resolve correctly — on the site austinpads.com. WHY IT MATTERS Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||