A prioritized, living to-do list for askemai.com, built from this site's sources and current trends in Artificial Intelligence. 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 askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Lock down sensitive data — nothing private is publicly reachable — on the site askemai.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 askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site askemai.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 | 98 | Security | 2026-06-20 | on askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site askemai.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 | 97 | Flagship | 2026-06-21 | on askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site askemai.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 Artificial Intelligence — 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 Artificial Intelligence 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 askemai.com Build the definitive Artificial Intelligence cornerstone guide |
Create the single most useful, authoritative page on Artificial Intelligence 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Build the definitive Artificial Intelligence cornerstone guide — on the site askemai.com. WHY IT MATTERS Create the single most useful, authoritative page on Artificial Intelligence 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 Artificial Intelligence — 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 Artificial Intelligence 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 | 90 | Flagship | 2026-06-26 | on askemai.com Add an interactive tool and an email capture for Artificial Intelligence |
Build one genuinely useful interactive element for Artificial Intelligence (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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Add an interactive tool and an email capture for Artificial Intelligence — on the site askemai.com. WHY IT MATTERS Build one genuinely useful interactive element for Artificial Intelligence (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 Artificial Intelligence — 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 Artificial Intelligence 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 | 89 | Trends | 2026-06-26 | on askemai.com Publish: The latest frontier AI model tier and what it unlocks |
Trending angle in Artificial Intelligence. 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Publish: The latest frontier AI model tier and what it unlocks — on the site askemai.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 8 | 86 | Popularity | 2026-06-28 | on askemai.com Build a plain-English AI answers library |
Publish one tight page per real beginner question — what is a token, why do chatbots make things up, is my data used for training — written at newspaper reading level with a 40-word direct answer up top. The ask-style domain earns its name only if it actually answers. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Build a plain-English AI answers library — on the site askemai.com. WHY IT MATTERS Publish one tight page per real beginner question — what is a token, why do chatbots make things up, is my data used for training — written at newspaper reading level with a 40-word direct answer up top. The ask-style domain earns its name only if it actually answers. (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 | 84 | Popularity | 2026-06-30 | on askemai.com Weekly what-changed-in-AI digest via gen-live.py |
Wire a weekly plain-language roundup of genuinely notable AI developments through the mass-content engine, each item summarized in two sentences with a clean source link. Fresh dated pages give the site a heartbeat in Google News-adjacent surfaces and a reason for return visits. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Weekly what-changed-in-AI digest via gen-live.py — on the site askemai.com. WHY IT MATTERS Wire a weekly plain-language roundup of genuinely notable AI developments through the mass-content engine, each item summarized in two sentences with a clean source link. Fresh dated pages give the site a heartbeat in Google News-adjacent surfaces and a reason for return visits. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 83 | Trends | 2026-06-30 | on askemai.com Publish: Agentic workflows a small business can deploy this month |
Trending angle in Artificial Intelligence. 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Publish: Agentic workflows a small business can deploy this month — on the site askemai.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 83 | Trends | 2026-06-30 | on askemai.com Publish: Answer-engine optimization — getting cited by AI search |
Trending angle in Artificial Intelligence. 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Publish: Answer-engine optimization — getting cited by AI search — on the site askemai.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence 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 | 82 | Popularity | 2026-07-01 | on askemai.com Comparison explainers for the decisions people face |
Write honest side-by-side pages for choices real users make — chatbot subscription tiers, free versus paid assistants, phone versus desktop AI apps — grounded in published pricing and features only. Comparison queries carry the most traffic in consumer AI and few sites answer them without hype. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Comparison explainers for the decisions people face — on the site askemai.com. WHY IT MATTERS Write honest side-by-side pages for choices real users make — chatbot subscription tiers, free versus paid assistants, phone versus desktop AI apps — grounded in published pricing and features only. Comparison queries carry the most traffic in consumer AI and few sites answer them without hype. (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 | 78 | Trends | 2026-07-04 | on askemai.com Publish: Practical AI guardrails and what to avoid |
Trending angle in Artificial Intelligence. 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Publish: Practical AI guardrails and what to avoid — on the site askemai.com. WHY IT MATTERS Trending angle in Artificial Intelligence. 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 Artificial Intelligence 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 | 76 | Revenue | 2026-07-05 | on askemai.com Amazon shelf of accessible AI books |
Curate readable AI titles — introductions, ethics, practical guides — with the colinfirthfan-20 tag and a two-line honest review each. Book recommendations fit an explainer site natively, and the elder-friendly framing (which books will not overwhelm a beginner) is a differentiator no big tech blog offers. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Amazon shelf of accessible AI books — on the site askemai.com. WHY IT MATTERS Curate readable AI titles — introductions, ethics, practical guides — with the colinfirthfan-20 tag and a two-line honest review each. Book recommendations fit an explainer site natively, and the elder-friendly framing (which books will not overwhelm a beginner) is a differentiator no big tech blog offers. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 15 | 75 | Revenue | 2026-07-06 | on askemai.com AdSense placed below the answer, never above |
Run pub-7759195213529699 on the answers library with units strictly after the direct-answer block, so no visitor scrolls past an ad to reach the answer they came for. Answer-first placement protects the site's core promise while the library's long-tail traffic still monetizes. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) AdSense placed below the answer, never above — on the site askemai.com. WHY IT MATTERS Run pub-7759195213529699 on the answers library with units strictly after the direct-answer block, so no visitor scrolls past an ad to reach the answer they came for. Answer-first placement protects the site's core promise while the library's long-tail traffic still monetizes. (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 | 74 | Content | 2026-07-07 | on askemai.com Deepen the main Artificial Intelligence 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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Deepen the main Artificial Intelligence guide with current data and examples — on the site askemai.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 Artificial Intelligence 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 Artificial Intelligence. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 17 | 74 | Revenue | 2026-07-07 | on askemai.com Newsletter widget capturing the weekly-digest audience |
Embed wholetech.com/newsletter/widget.js on every answer page with the pitch: one plain-English AI update a week, no jargon. The digest content already exists; the list becomes the durable asset and future sponsorship inventory. Signups drive DRAFT notifications only, per network rules. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Newsletter widget capturing the weekly-digest audience — on the site askemai.com. WHY IT MATTERS Embed wholetech.com/newsletter/widget.js on every answer page with the pitch: one plain-English AI update a week, no jargon. The digest content already exists; the list becomes the durable asset and future sponsorship inventory. Signups drive DRAFT notifications only, per network rules. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 18 | 72 | Design | 2026-07-08 | on askemai.com Conversation-card aesthetic: question bubbles, typewriter answers |
Art-direct each page as a dialogue: the question set in a rounded speech-bubble card, the answer beneath in calm typewriter-adjacent monospace on warm paper white, with a thin cursor-line accent. It visually embodies asking, which no generic tech-blog template does. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Conversation-card aesthetic: question bubbles, typewriter answers — on the site askemai.com. WHY IT MATTERS Art-direct each page as a dialogue: the question set in a rounded speech-bubble card, the answer beneath in calm typewriter-adjacent monospace on warm paper white, with a thin cursor-line accent. It visually embodies asking, which no generic tech-blog template does. (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 | 72 | Sources | 2026-07-08 | on askemai.com Build /sources/ out to at least 10 authoritative links |
Only 4 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Build /sources/ out to at least 10 authoritative links — on the site askemai.com. WHY IT MATTERS Only 4 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Artificial Intelligence. 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 Artificial Intelligence 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. | ||||
| 20 | 67 | AEO | 2026-07-12 | on askemai.com QAPage schema plus llms.txt on an answers site |
This domain is answer-engine bait by design: add QAPage or FAQPage JSON-LD to every library entry, publish llms.txt describing the library, keep both sitemaps current, and ping IndexNow on each new answer. Target 95-plus on af-deploy.py — an ask-site should top the AF scorer. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) QAPage schema plus llms.txt on an answers site — on the site askemai.com. WHY IT MATTERS This domain is answer-engine bait by design: add QAPage or FAQPage JSON-LD to every library entry, publish llms.txt describing the library, keep both sitemaps current, and ping IndexNow on each new answer. Target 95-plus on af-deploy.py — an ask-site should top the AF scorer. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 67 | Content | 2026-07-12 | on askemai.com Add an FAQ answering the top questions in Artificial Intelligence |
Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Add an FAQ answering the top questions in Artificial Intelligence — on the site askemai.com. WHY IT MATTERS Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Artificial Intelligence 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 Artificial Intelligence. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 65 | Design | 2026-07-13 | on askemai.com Glossary tooltips styled as marginalia notes |
Every technical term gets an underlined dotted style that opens a hand-note-styled margin definition — sepia sticky-note card, slight rotation. Inline glossing keeps beginners on the page instead of bouncing to search a term, and the marginalia look reinforces the friendly-explainer identity. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Glossary tooltips styled as marginalia notes — on the site askemai.com. WHY IT MATTERS Every technical term gets an underlined dotted style that opens a hand-note-styled margin definition — sepia sticky-note card, slight rotation. Inline glossing keeps beginners on the page instead of bouncing to search a term, and the marginalia look reinforces the friendly-explainer identity. (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. | ||||
| 23 | 63 | Product | 2026-07-14 | on askemai.com An honest ask box that routes to drafts |
Add a question-submission form whose entries create Gmail DRAFT notifications for Paul, feeding the editorial queue — never an on-site paid AI backend, which would violate the subscription-only rule. Reader questions become next week's answer pages, closing the loop that makes the library grow itself. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) An honest ask box that routes to drafts — on the site askemai.com. WHY IT MATTERS Add a question-submission form whose entries create Gmail DRAFT notifications for Paul, feeding the editorial queue — never an on-site paid AI backend, which would violate the subscription-only rule. Reader questions become next week's answer pages, closing the loop that makes the library grow itself. (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. | ||||
| 24 | 59 | Design | 2026-07-17 | on askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site askemai.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. | ||||
| 25 | 55 | SEO | 2026-07-20 | on askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site askemai.com. WHY IT MATTERS Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 26 | 54 | Fresh | 2026-07-21 | on askemai.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Keep the live / news feed updated on cadence (2×/day) — on the site askemai.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Artificial Intelligence: 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 Artificial Intelligence 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. | ||||
| 27 | 50 | SEO | 2026-07-24 | on askemai.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Add Article + FAQ structured data — on the site askemai.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. | ||||
| 28 | 43 | SEO | 2026-07-28 | on askemai.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 askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site askemai.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. | ||||
| 29 | 42 | Monetize | 2026-07-29 | on askemai.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Add the network affiliate + AdSense setup — on the site askemai.com. WHY IT MATTERS Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. HOW TO APPROACH IT 1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup. 2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Links resolve and can earn, and placement is tasteful and does not hurt the reading experience. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 30 | 42 | Video | 2026-07-29 | on askemai.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. ★ Copy-paste prompt for askemai.com You are working on ONE specific website: askemai.com (live at https://askemai.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/askemai.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for askemai.com and no other site — make all changes on askemai.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on askemai.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site askemai.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Artificial Intelligence 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. | ||||