A prioritized, living to-do list for podsat.com, built from this site's sources and current trends in Audio & Video Production. 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 podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site podsat.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. | ||||
| 2 | 97 | Security | 2026-06-21 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Lock down sensitive data — nothing private is publicly reachable — on the site podsat.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. | ||||
| 3 | 97 | Security | 2026-06-21 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site podsat.com. WHY IT MATTERS Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it. HOW TO APPROACH IT 1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200. 2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public. 3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy). 4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A logged-out request to every sensitive path returns 403/404 — verified, not assumed. - No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON. - HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 4 | 94 | Flagship | 2026-06-23 | on podsat.com Build the definitive Audio & Video Production cornerstone guide |
Create the single most useful, authoritative page on Audio & Video Production 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Build the definitive Audio & Video Production cornerstone guide — on the site podsat.com. WHY IT MATTERS Create the single most useful, authoritative page on Audio & Video Production 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 Audio & Video Production — 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 Audio & Video Production 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 | Flagship | 2026-06-23 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site podsat.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 Audio & Video Production — 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 Audio & Video Production resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 92 | Trends | 2026-06-24 | on podsat.com Publish: The gear and codecs worth upgrading to now |
Trending angle in Audio & Video Production. 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Publish: The gear and codecs worth upgrading to now — on the site podsat.com. WHY IT MATTERS Trending angle in Audio & Video Production. 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 Audio & Video Production 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 podsat.com Add an interactive tool and an email capture for Audio & Video Production |
Build one genuinely useful interactive element for Audio & Video Production (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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Add an interactive tool and an email capture for Audio & Video Production — on the site podsat.com. WHY IT MATTERS Build one genuinely useful interactive element for Audio & Video Production (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 Audio & Video Production — 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 Audio & Video Production 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 | 88 | Popularity | 2026-06-27 | on podsat.com Studio-setup guides at three honest budget tiers |
Publish three definitive builds — closet podcast rig, serious home studio, small video suite — with exact gear lists, wiring order, and room-treatment notes. Budget-tiered setup guides are the perennial entry query for audio production and the natural spine for every other page. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Studio-setup guides at three honest budget tiers — on the site podsat.com. WHY IT MATTERS Publish three definitive builds — closet podcast rig, serious home studio, small video suite — with exact gear lists, wiring order, and room-treatment notes. Budget-tiered setup guides are the perennial entry query for audio production and the natural spine for every other page. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 9 | 88 | Trends | 2026-06-27 | on podsat.com Publish: AI editing and transcription in the production pipeline |
Trending angle in Audio & Video Production. 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Publish: AI editing and transcription in the production pipeline — on the site podsat.com. WHY IT MATTERS Trending angle in Audio & Video Production. 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 Audio & Video Production reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 86 | Popularity | 2026-06-28 | on podsat.com /videos/ page of embeddable studio walkthroughs |
Build a /videos/ page using the network's yt-dlp pipeline of real studio tours and mic-technique demos, verifying every embed with check-embed.mjs and dropping embed=false entries. Video walkthroughs keep session times long and give the gear guides visual proof. Renumber cleanly after dropping any dead embeds. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) /videos/ page of embeddable studio walkthroughs — on the site podsat.com. WHY IT MATTERS Build a /videos/ page using the network's yt-dlp pipeline of real studio tours and mic-technique demos, verifying every embed with check-embed.mjs and dropping embed=false entries. Video walkthroughs keep session times long and give the gear guides visual proof. Renumber cleanly after dropping any dead embeds. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 82 | Trends | 2026-07-01 | on podsat.com Publish: Livestream setups that punch above their cost |
Trending angle in Audio & Video Production. 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Publish: Livestream setups that punch above their cost — on the site podsat.com. WHY IT MATTERS Trending angle in Audio & Video Production. 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 Audio & Video Production 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 | 81 | Revenue | 2026-07-02 | on podsat.com Amazon gear links throughout guides and shootouts |
Tag every recommended interface, mic, boom arm, and acoustic panel with colinfirthfan-20, disclosed. Podcast-gear content is prime affiliate territory: readers arrive mid-purchase-decision with $100–600 budgets, and the tiered guides map exactly onto Amazon cart compositions. Refresh links when models are superseded so recommendations never point at discontinued gear. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Amazon gear links throughout guides and shootouts — on the site podsat.com. WHY IT MATTERS Tag every recommended interface, mic, boom arm, and acoustic panel with colinfirthfan-20, disclosed. Podcast-gear content is prime affiliate territory: readers arrive mid-purchase-decision with $100–600 budgets, and the tiered guides map exactly onto Amazon cart compositions. Refresh links when models are superseded so recommendations never point at discontinued gear. (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 | Popularity | 2026-07-03 | on podsat.com Mic shootout pages with recorded A/B clips |
For classic matchups — SM7B vs RE20, USB vs XLR interfaces — publish comparison pages with genuinely recorded audio clips, not claimed impressions. Real A/B audio is scarce online, earns forum citations from r/audioengineering and podcast communities, and directly precedes purchase decisions. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Mic shootout pages with recorded A/B clips — on the site podsat.com. WHY IT MATTERS For classic matchups — SM7B vs RE20, USB vs XLR interfaces — publish comparison pages with genuinely recorded audio clips, not claimed impressions. Real A/B audio is scarce online, earns forum citations from r/audioengineering and podcast communities, and directly precedes purchase decisions. (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 | 79 | Trends | 2026-07-03 | on podsat.com Publish: Color / audio workflows pros are adopting |
Trending angle in Audio & Video Production. 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Publish: Color / audio workflows pros are adopting — on the site podsat.com. WHY IT MATTERS Trending angle in Audio & Video Production. 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 Audio & Video Production 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 | 75 | Content | 2026-07-06 | on podsat.com Deepen the main Audio & Video Production 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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Deepen the main Audio & Video Production guide with current data and examples — on the site podsat.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 Audio & Video Production 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 Audio & Video Production. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 16 | 75 | Revenue | 2026-07-06 | on podsat.com Disclosed AdSense on troubleshooting and explainer pages |
Run pub-7759195213529699 on the problem-solving library — 'why does my podcast sound echoey', 'fix USB mic latency' — where visitors arrive from search without purchase intent. Troubleshooting traffic monetizes via ads; leave the affiliate-heavy gear pages ad-free to protect conversion. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Disclosed AdSense on troubleshooting and explainer pages — on the site podsat.com. WHY IT MATTERS Run pub-7759195213529699 on the problem-solving library — 'why does my podcast sound echoey', 'fix USB mic latency' — where visitors arrive from search without purchase intent. Troubleshooting traffic monetizes via ads; leave the affiliate-heavy gear pages ad-free to protect conversion. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 17 | 70 | Design | 2026-07-10 | on podsat.com Broadcast-console aesthetic: VU meters and ON-AIR red |
Art-direct as a live control room: VU-meter bars as section dividers, waveform strips under headers, XLR and patch-cable iconography, an 'ON AIR' red reserved for calls-to-action on matte-black console texture. The site should feel rack-mounted, not bloggy. Reserve the red strictly for one action per page. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Broadcast-console aesthetic: VU meters and ON-AIR red — on the site podsat.com. WHY IT MATTERS Art-direct as a live control room: VU-meter bars as section dividers, waveform strips under headers, XLR and patch-cable iconography, an 'ON AIR' red reserved for calls-to-action on matte-black console texture. The site should feel rack-mounted, not bloggy. Reserve the red strictly for one action per page. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 18 | 70 | Design | 2026-07-10 | on podsat.com Gear cards styled as channel strips |
Present each recommended item as a mixer channel strip — fader graphic showing price tier, knobs encoding specs (pattern, connectivity), a scribble-strip label in grease-pencil type. It compresses comparison data into the niche's native visual grammar and makes roundups scannable. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Gear cards styled as channel strips — on the site podsat.com. WHY IT MATTERS Present each recommended item as a mixer channel strip — fader graphic showing price tier, knobs encoding specs (pattern, connectivity), a scribble-strip label in grease-pencil type. It compresses comparison data into the niche's native visual grammar and makes roundups scannable. (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 | 70 | Revenue | 2026-07-10 | on podsat.com Local production-services listing with drafted inquiries |
A page offering editing, remote-recording direction, and Austin session help, with an inquiry form whose submissions become Gmail DRAFTS for review — never auto-sent. Services capture the visitors gear content can't: people who'd rather pay someone than learn Reaper. List real turnaround times, no inflated promises. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Local production-services listing with drafted inquiries — on the site podsat.com. WHY IT MATTERS A page offering editing, remote-recording direction, and Austin session help, with an inquiry form whose submissions become Gmail DRAFTS for review — never auto-sent. Services capture the visitors gear content can't: people who'd rather pay someone than learn Reaper. List real turnaround times, no inflated promises. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 69 | Content | 2026-07-10 | on podsat.com Add an FAQ answering the top questions in Audio & Video Production |
Pull the real questions people ask in Audio & Video Production and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Add an FAQ answering the top questions in Audio & Video Production — on the site podsat.com. WHY IT MATTERS Pull the real questions people ask in Audio & Video Production and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Audio & Video Production 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 Audio & Video Production. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 61 | AEO | 2026-07-16 | on podsat.com FAQ schema on beginner podcast-gear questions |
FAQPage JSON-LD answering 'what mic should a beginner podcaster buy', 'do I need an audio interface', 'how do I stop echo' in direct, citable answers tied to the guides. Run af-deploy.py to 90+; gear questions are among the most assistant-asked queries in this niche. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) FAQ schema on beginner podcast-gear questions — on the site podsat.com. WHY IT MATTERS FAQPage JSON-LD answering 'what mic should a beginner podcaster buy', 'do I need an audio interface', 'how do I stop echo' in direct, citable answers tied to the guides. Run af-deploy.py to 90+; gear questions are among the most assistant-asked queries in this niche. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 59 | Product | 2026-07-17 | on podsat.com Studio-budget calculator building a shoppable list |
A client-side tool: pick show format, room type, and budget; it assembles a compatible gear list with running total, each line linking via colinfirthfan-20. It converts the guides' logic into a personal answer and is the page podcasting communities will link when beginners ask. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Studio-budget calculator building a shoppable list — on the site podsat.com. WHY IT MATTERS A client-side tool: pick show format, room type, and budget; it assembles a compatible gear list with running total, each line linking via colinfirthfan-20. It converts the guides' logic into a personal answer and is the page podcasting communities will link when beginners ask. (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 | 58 | Design | 2026-07-18 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site podsat.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 | 57 | Sources | 2026-07-19 | on podsat.com Add source: ProSoundWeb |
Live & installed sound Authoritative Audio & Video Production reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Add source: ProSoundWeb — on the site podsat.com. WHY IT MATTERS Live & installed sound Authoritative Audio & Video Production reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Audio & Video Production. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Audio & Video Production expert would trust. - 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 | 55 | Fresh | 2026-07-20 | on podsat.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Audio & Video Production items and pinging IndexNow each run. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Keep the live / news feed updated on cadence (2×/day) — on the site podsat.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Audio & Video Production items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Audio & Video Production: 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 Audio & Video Production items on schedule and is discovered quickly. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 26 | 52 | SEO | 2026-07-22 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site podsat.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. | ||||
| 27 | 51 | Sources | 2026-07-23 | on podsat.com Add source: Newsshooter |
Pro video gear news Authoritative Audio & Video Production reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Add source: Newsshooter — on the site podsat.com. WHY IT MATTERS Pro video gear news Authoritative Audio & Video Production reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Audio & Video Production. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Audio & Video Production expert would trust. - 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 | 49 | SEO | 2026-07-24 | on podsat.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Add Article + FAQ structured data — on the site podsat.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. | ||||
| 29 | 44 | Monetize | 2026-07-28 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Verify affiliate links and ad placement resolve correctly — on the site podsat.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. | ||||
| 30 | 44 | SEO | 2026-07-28 | on podsat.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 podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site podsat.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. | ||||
| 31 | 40 | Video | 2026-07-31 | on podsat.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Audio & Video Production videos. Re-verify embeds. ★ Copy-paste prompt for podsat.com You are working on ONE specific website: podsat.com (live at https://podsat.com/), a Audio & Video Production site in the WholeTech network, served from /var/www/podsat.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for podsat.com and no other site — make all changes on podsat.com. Act like a senior editor and web engineer who knows the Audio & Video Production niche cold. GOAL (on podsat.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site podsat.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Audio & Video Production videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Audio & Video Production 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. | ||||