A prioritized, living to-do list for robopodcast.com, built from this site's sources and current trends in Robotics. 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 robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Lock down sensitive data — nothing private is publicly reachable — on the site robopodcast.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 | 99 | Security | 2026-06-19 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site robopodcast.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 | 97 | Flagship | 2026-06-21 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site robopodcast.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 Robotics — 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 Robotics 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 | 97 | Security | 2026-06-21 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site robopodcast.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. | ||||
| 5 | 93 | Flagship | 2026-06-23 | on robopodcast.com Build the definitive Robotics cornerstone guide |
Create the single most useful, authoritative page on Robotics 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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Build the definitive Robotics cornerstone guide — on the site robopodcast.com. WHY IT MATTERS Create the single most useful, authoritative page on Robotics 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 Robotics — 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 Robotics 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 | 93 | Flagship | 2026-06-23 | on robopodcast.com Add an interactive tool and an email capture for Robotics |
Build one genuinely useful interactive element for Robotics (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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Add an interactive tool and an email capture for Robotics — on the site robopodcast.com. WHY IT MATTERS Build one genuinely useful interactive element for Robotics (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 Robotics — 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 Robotics resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 91 | Popularity | 2026-06-25 | on robopodcast.com Sortable directory of real robotics podcasts |
Build the definitive index of actual robotics shows — The Robot Report Podcast, Sense Think Act, Lex Fridman's robotics episodes — as a sortable worksheet table (alldomains pattern) with focus, cadence, and standout-episode picks. A maintained directory outranks any single review post and earns citations from the shows themselves. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Sortable directory of real robotics podcasts — on the site robopodcast.com. WHY IT MATTERS Build the definitive index of actual robotics shows — The Robot Report Podcast, Sense Think Act, Lex Fridman's robotics episodes — as a sortable worksheet table (alldomains pattern) with focus, cadence, and standout-episode picks. A maintained directory outranks any single review post and earns citations from the shows themselves. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 8 | 88 | Popularity | 2026-06-27 | on robopodcast.com Weekly three-episodes-worth-your-commute roundup |
Publish a short weekly page picking three genuinely strong robotics episodes with two-sentence honest reasons to listen, fed into the newsletter widget. Recurring curation builds return visits and gives podcast hosts a reason to share the site when their episode makes the cut. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Weekly three-episodes-worth-your-commute roundup — on the site robopodcast.com. WHY IT MATTERS Publish a short weekly page picking three genuinely strong robotics episodes with two-sentence honest reasons to listen, fed into the newsletter widget. Recurring curation builds return visits and gives podcast hosts a reason to share the site when their episode makes the cut. (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 | 87 | Trends | 2026-06-28 | on robopodcast.com Publish: A current, data-backed explainer in Robotics |
Trending angle in Robotics. 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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Publish: A current, data-backed explainer in Robotics — on the site robopodcast.com. WHY IT MATTERS Trending angle in Robotics. 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 Robotics 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 | 84 | Popularity | 2026-06-30 | on robopodcast.com Videos page of embeddable robotics interviews |
Add a /videos/ page of robotics talks and long-form interviews, every embed verified with check-embed.mjs so nothing renders as a dead player. Video keeps directory visitors on-site longer and captures the audience that prefers watching researchers and founders over audio-only listening. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Videos page of embeddable robotics interviews — on the site robopodcast.com. WHY IT MATTERS Add a /videos/ page of robotics talks and long-form interviews, every embed verified with check-embed.mjs so nothing renders as a dead player. Video keeps directory visitors on-site longer and captures the audience that prefers watching researchers and founders over audio-only listening. (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 | 83 | Trends | 2026-06-30 | on robopodcast.com Publish: The question your Robotics audience is searching most right now |
Trending angle in Robotics. 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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Publish: The question your Robotics audience is searching most right now — on the site robopodcast.com. WHY IT MATTERS Trending angle in Robotics. 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 Robotics 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 robopodcast.com Listening-gear and robotics-books shelf via Amazon |
Create colinfirthfan-20 pages that fit the audience honestly: commute headphones and podcast-listening gear, plus a books shelf of titles actually discussed on the indexed shows. Tie each book to the episode that covered it so recommendations feel earned rather than bolted on. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Listening-gear and robotics-books shelf via Amazon — on the site robopodcast.com. WHY IT MATTERS Create colinfirthfan-20 pages that fit the audience honestly: commute headphones and podcast-listening gear, plus a books shelf of titles actually discussed on the indexed shows. Tie each book to the episode that covered it so recommendations feel earned rather than bolted on. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 80 | Trends | 2026-07-03 | on robopodcast.com Publish: A 'what changed in 2026' round-up for Robotics |
Trending angle in Robotics. 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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Publish: A 'what changed in 2026' round-up for Robotics — on the site robopodcast.com. WHY IT MATTERS Trending angle in Robotics. 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 Robotics reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 14 | 75 | Content | 2026-07-06 | on robopodcast.com Deepen the main Robotics 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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Deepen the main Robotics guide with current data and examples — on the site robopodcast.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 Robotics 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 Robotics. - 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. | ||||
| 15 | 73 | Revenue | 2026-07-07 | on robopodcast.com AdSense on directory and roundup pages |
Once the directory and a few weeks of roundups establish content depth, add pub-7759195213529699 units on those pages. Podcast-discovery traffic is informational and tolerates tasteful display ads well; keep units out of the directory table itself so the sortable worksheet stays clean and fast. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) AdSense on directory and roundup pages — on the site robopodcast.com. WHY IT MATTERS Once the directory and a few weeks of roundups establish content depth, add pub-7759195213529699 units on those pages. Podcast-discovery traffic is informational and tolerates tasteful display ads well; keep units out of the directory table itself so the sortable worksheet stays clean and fast. (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 | 72 | Revenue | 2026-07-08 | on robopodcast.com Publish an honest sponsor-slot rate card |
Create a /sponsor/ page defining one clearly-labeled slot in the weekly roundup and newsletter, with transparent placement rules and current audience numbers only once real. No invented reach claims — just documented inventory, so when a robotics company or tool vendor arrives, the deal is one email away. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Publish an honest sponsor-slot rate card — on the site robopodcast.com. WHY IT MATTERS Create a /sponsor/ page defining one clearly-labeled slot in the weekly roundup and newsletter, with transparent placement rules and current audience numbers only once real. No invented reach claims — just documented inventory, so when a robotics company or tool vendor arrives, the deal is one email away. (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 | 67 | Content | 2026-07-12 | on robopodcast.com Add an FAQ answering the top questions in Robotics |
Pull the real questions people ask in Robotics and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Add an FAQ answering the top questions in Robotics — on the site robopodcast.com. WHY IT MATTERS Pull the real questions people ask in Robotics and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Robotics 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 Robotics. - 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. | ||||
| 18 | 67 | Design | 2026-07-12 | on robopodcast.com Waveform-as-circuit-trace visual system |
Art-direct the audio-meets-robots overlap: audio waveforms drawn like PCB copper traces, LED VU-meter accent bars, a dark control-room console palette with phosphor-green highlights. It instantly says 'robotics listening station' rather than generic podcast blog, and no competing directory looks anything like it. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Waveform-as-circuit-trace visual system — on the site robopodcast.com. WHY IT MATTERS Art-direct the audio-meets-robots overlap: audio waveforms drawn like PCB copper traces, LED VU-meter accent bars, a dark control-room console palette with phosphor-green highlights. It instantly says 'robotics listening station' rather than generic podcast blog, and no competing directory looks anything like it. (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 | 65 | AEO | 2026-07-13 | on robopodcast.com PodcastSeries schema plus best-of direct answers |
Mark up every directory entry with PodcastSeries/PodcastEpisode schema and add a direct-answer block for 'best robotics podcasts 2026' summarizing the top picks with one-line reasons. Agents assembling listening recommendations will lift and cite the structured list; run af-deploy.py to ninety-plus. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) PodcastSeries schema plus best-of direct answers — on the site robopodcast.com. WHY IT MATTERS Mark up every directory entry with PodcastSeries/PodcastEpisode schema and add a direct-answer block for 'best robotics podcasts 2026' summarizing the top picks with one-line reasons. Agents assembling listening recommendations will lift and cite the structured list; run af-deploy.py to ninety-plus. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 65 | Design | 2026-07-13 | on robopodcast.com Episode cards styled as cassette labels |
Render episode picks as cassette or DAT-tape label cards: show name in label type, runtime, guest, and topic chips (humanoids, drones, industry) as colored tape stripes. A consistent physical-media metaphor makes the weekly roundup visually collectible and screenshot-friendly for social sharing. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Episode cards styled as cassette labels — on the site robopodcast.com. WHY IT MATTERS Render episode picks as cassette or DAT-tape label cards: show name in label type, runtime, guest, and topic chips (humanoids, drones, industry) as colored tape stripes. A consistent physical-media metaphor makes the weekly roundup visually collectible and screenshot-friendly for social sharing. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 60 | Fresh | 2026-07-17 | on robopodcast.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Robotics items and pinging IndexNow each run. ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Keep the live / news feed updated on cadence (2×/day) — on the site robopodcast.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Robotics items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Robotics: 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 Robotics 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. | ||||
| 22 | 58 | Product | 2026-07-18 | on robopodcast.com Machine-readable episodes and shows JSON feed |
Expose the curated directory as /api/shows.json — show, feed URL, focus tags, latest standout episode — refreshed when the roundup publishes. Agents and podcast apps can consume the curation directly, which is exactly the Agents-First posture, and the feed costs nothing beyond the data already maintained. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Machine-readable episodes and shows JSON feed — on the site robopodcast.com. WHY IT MATTERS Expose the curated directory as /api/shows.json — show, feed URL, focus tags, latest standout episode — refreshed when the roundup publishes. Agents and podcast apps can consume the curation directly, which is exactly the Agents-First posture, and the feed costs nothing beyond the data already maintained. (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 | 55 | Design | 2026-07-20 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site robopodcast.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 | 51 | SEO | 2026-07-23 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site robopodcast.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. | ||||
| 25 | 49 | SEO | 2026-07-24 | on robopodcast.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Add Article + FAQ structured data — on the site robopodcast.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. | ||||
| 26 | 44 | SEO | 2026-07-28 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site robopodcast.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. | ||||
| 27 | 44 | Video | 2026-07-28 | on robopodcast.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Robotics videos. Re-verify embeds. ★ Copy-paste prompt for robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site robopodcast.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Robotics videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Robotics videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 42 | Monetize | 2026-07-29 | on robopodcast.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 robopodcast.com You are working on ONE specific website: robopodcast.com (live at https://robopodcast.com/), a Robotics site in the WholeTech network, served from /var/www/robopodcast.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for robopodcast.com and no other site — make all changes on robopodcast.com. Act like a senior editor and web engineer who knows the Robotics niche cold. GOAL (on robopodcast.com) Verify affiliate links and ad placement resolve correctly — on the site robopodcast.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. | ||||