A prioritized, living to-do list for muskmile.com, built from this site's sources and current trends in Tesla & EVs. 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 muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Lock down sensitive data — nothing private is publicly reachable — on the site muskmile.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 muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site muskmile.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 | 96 | Security | 2026-06-21 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site muskmile.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 | 95 | Flagship | 2026-06-22 | on muskmile.com Build the definitive Tesla & EVs cornerstone guide |
Create the single most useful, authoritative page on Tesla & EVs 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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Build the definitive Tesla & EVs cornerstone guide — on the site muskmile.com. WHY IT MATTERS Create the single most useful, authoritative page on Tesla & EVs 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 Tesla & EVs — 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 Tesla & EVs 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 | 95 | Flagship | 2026-06-22 | on muskmile.com Add an interactive tool and an email capture for Tesla & EVs |
Build one genuinely useful interactive element for Tesla & EVs (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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Add an interactive tool and an email capture for Tesla & EVs — on the site muskmile.com. WHY IT MATTERS Build one genuinely useful interactive element for Tesla & EVs (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 Tesla & EVs — 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 Tesla & EVs resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 92 | Flagship | 2026-06-24 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site muskmile.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 Tesla & EVs — 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 Tesla & EVs 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 muskmile.com Giga Texas and Robotaxi local coverage beat |
Own the Austin angle no national EV site has locally: Giga Texas expansion filings, Robotaxi service-area changes, Supercharger openings along I-35 — factual short posts from public records and observable rollouts. Paul's Austin footing makes this the site's genuinely defensible beat. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Giga Texas and Robotaxi local coverage beat — on the site muskmile.com. WHY IT MATTERS Own the Austin angle no national EV site has locally: Giga Texas expansion filings, Robotaxi service-area changes, Supercharger openings along I-35 — factual short posts from public records and observable rollouts. Paul's Austin footing makes this the site's genuinely defensible beat. (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 | 90 | Trends | 2026-06-26 | on muskmile.com Publish: A current, data-backed explainer in Tesla & EVs |
Trending angle in Tesla & EVs. 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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Publish: A current, data-backed explainer in Tesla & EVs — on the site muskmile.com. WHY IT MATTERS Trending angle in Tesla & EVs. 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 Tesla & EVs 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. | ||||
| 9 | 87 | Popularity | 2026-06-28 | on muskmile.com Automated EV news via the live engine |
Point /root/gen-live.py at Tesla and EV-industry feeds — delivery numbers, price changes, charging-network news — publishing a /live/ Google-News-structured section. EV news cycles hourly; the mass-content engine keeps the domain perpetually fresh between hand-written Austin pieces. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Automated EV news via the live engine — on the site muskmile.com. WHY IT MATTERS Point /root/gen-live.py at Tesla and EV-industry feeds — delivery numbers, price changes, charging-network news — publishing a /live/ Google-News-structured section. EV news cycles hourly; the mass-content engine keeps the domain perpetually fresh between hand-written Austin pieces. (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 | 86 | Trends | 2026-06-28 | on muskmile.com Publish: The question your Tesla & EVs audience is searching most right now |
Trending angle in Tesla & EVs. 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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Publish: The question your Tesla & EVs audience is searching most right now — on the site muskmile.com. WHY IT MATTERS Trending angle in Tesla & EVs. 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 Tesla & EVs 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 | Popularity | 2026-06-30 | on muskmile.com Verified embeddable Tesla review video hub |
Build /videos/ around genuinely watchable Tesla and EV road-test videos, running every candidate through check-embed.mjs and dropping embed=false IDs before renumbering. EV shoppers binge review video; a curated hub that never shows a broken player earns return visits. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Verified embeddable Tesla review video hub — on the site muskmile.com. WHY IT MATTERS Build /videos/ around genuinely watchable Tesla and EV road-test videos, running every candidate through check-embed.mjs and dropping embed=false IDs before renumbering. EV shoppers binge review video; a curated hub that never shows a broken player earns 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. | ||||
| 12 | 81 | Revenue | 2026-07-02 | on muskmile.com Amazon EV-accessory gear guides |
Publish accessory guides with tag colinfirthfan-20 — J1772 adapter locks, trunk organizers, all-weather mats, portable tire inflators, home-charger mounting hardware — each reviewed within an ownership-tips article. EV owners buy accessories in the first ninety days; guides aimed there convert honestly. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Amazon EV-accessory gear guides — on the site muskmile.com. WHY IT MATTERS Publish accessory guides with tag colinfirthfan-20 — J1772 adapter locks, trunk organizers, all-weather mats, portable tire inflators, home-charger mounting hardware — each reviewed within an ownership-tips article. EV owners buy accessories in the first ninety days; guides aimed there convert honestly. (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 | 79 | Trends | 2026-07-03 | on muskmile.com Publish: A 'what changed in 2026' round-up for Tesla & EVs |
Trending angle in Tesla & EVs. 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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Publish: A 'what changed in 2026' round-up for Tesla & EVs — on the site muskmile.com. WHY IT MATTERS Trending angle in Tesla & EVs. 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 Tesla & EVs 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 | 74 | Revenue | 2026-07-07 | on muskmile.com Travala stays along Supercharger road-trip corridors |
Create road-trip corridor guides — Austin to Marfa, Texas to the Rockies — pairing Supercharger stops with disclosed Travala hotel links near each charging halt. Trip-planning is the one moment EV content and travel booking genuinely intersect, so the affiliate placement reads as service. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Travala stays along Supercharger road-trip corridors — on the site muskmile.com. WHY IT MATTERS Create road-trip corridor guides — Austin to Marfa, Texas to the Rockies — pairing Supercharger stops with disclosed Travala hotel links near each charging halt. Trip-planning is the one moment EV content and travel booking genuinely intersect, so the affiliate placement reads as service. (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 | 71 | Content | 2026-07-09 | on muskmile.com Deepen the main Tesla & EVs 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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Deepen the main Tesla & EVs guide with current data and examples — on the site muskmile.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 Tesla & EVs 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 Tesla & EVs. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 16 | 71 | Revenue | 2026-07-09 | on muskmile.com AdSense on evergreen ownership explainers |
Run pub-7759195213529699 on the evergreen library — charging-cost math, battery-degradation explainers, buying-used-Tesla checklists — where informational dwell time is long, keeping the /live/ news feed and calculators clean. Evergreen EV questions monetize steadily regardless of the news cycle. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) AdSense on evergreen ownership explainers — on the site muskmile.com. WHY IT MATTERS Run pub-7759195213529699 on the evergreen library — charging-cost math, battery-degradation explainers, buying-used-Tesla checklists — where informational dwell time is long, keeping the /live/ news feed and calculators clean. Evergreen EV questions monetize steadily regardless of the news cycle. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 17 | 69 | Design | 2026-07-10 | on muskmile.com Instrument-cluster aesthetic with regen-green accents |
Art-direct to the EV cockpit: matte near-black surfaces, thin gauge-arc motifs framing stat tiles, a single regen-green accent for positive deltas, and range-bar progress elements as the site's meter language. It should feel like reading a well-designed dash display, not a car blog. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Instrument-cluster aesthetic with regen-green accents — on the site muskmile.com. WHY IT MATTERS Art-direct to the EV cockpit: matte near-black surfaces, thin gauge-arc motifs framing stat tiles, a single regen-green accent for positive deltas, and range-bar progress elements as the site's meter language. It should feel like reading a well-designed dash display, not a car blog. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 18 | 66 | Design | 2026-07-12 | on muskmile.com Corridor maps styled as navigation screens |
Render the road-trip guides' maps in nav-screen style — dark basemap, glowing route ribbon, charger pins with stall counts and kW badges — matching the in-car planning experience readers already know. Consistent nav-styled maps become the site's screenshot signature on EV forums. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Corridor maps styled as navigation screens — on the site muskmile.com. WHY IT MATTERS Render the road-trip guides' maps in nav-screen style — dark basemap, glowing route ribbon, charger pins with stall counts and kW badges — matching the in-car planning experience readers already know. Consistent nav-styled maps become the site's screenshot signature on EV forums. (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 | Content | 2026-07-13 | on muskmile.com Add an FAQ answering the top questions in Tesla & EVs |
Pull the real questions people ask in Tesla & EVs and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Add an FAQ answering the top questions in Tesla & EVs — on the site muskmile.com. WHY IT MATTERS Pull the real questions people ask in Tesla & EVs and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Tesla & EVs 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 Tesla & EVs. - 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. | ||||
| 20 | 63 | Product | 2026-07-14 | on muskmile.com Cost-per-mile EV versus gas calculator |
Ship a client-side calculator comparing cost per mile: local electricity rate and EV efficiency against gas price and MPG, with a Texas-rate default preloaded. Shoppers run this exact math before buying; a clean tool earns links and anchors the ownership-cost content hub. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Cost-per-mile EV versus gas calculator — on the site muskmile.com. WHY IT MATTERS Ship a client-side calculator comparing cost per mile: local electricity rate and EV efficiency against gas price and MPG, with a Texas-rate default preloaded. Shoppers run this exact math before buying; a clean tool earns links and anchors the ownership-cost content hub. (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 | 61 | AEO | 2026-07-16 | on muskmile.com FAQ schema on charging-cost and range questions |
Mark up sourced answers — what a full Tesla charge costs at home versus Supercharging, real-world range in Texas heat — with FAQPage schema and run af-deploy.py above 90. These are among the highest-volume EV questions answer engines receive, and citable math wins. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) FAQ schema on charging-cost and range questions — on the site muskmile.com. WHY IT MATTERS Mark up sourced answers — what a full Tesla charge costs at home versus Supercharging, real-world range in Texas heat — with FAQPage schema and run af-deploy.py above 90. These are among the highest-volume EV questions answer engines receive, and citable math wins. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 59 | Design | 2026-07-17 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site muskmile.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. | ||||
| 23 | 57 | Fresh | 2026-07-19 | on muskmile.com Add a /live/ news feed for Tesla & EVs |
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Add a /live/ news feed for Tesla & EVs — on the site muskmile.com. WHY IT MATTERS An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Tesla & EVs: 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 Tesla & EVs 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. | ||||
| 24 | 52 | SEO | 2026-07-22 | on muskmile.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Add Article + FAQ structured data — on the site muskmile.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. | ||||
| 25 | 51 | SEO | 2026-07-23 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site muskmile.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 | 44 | Video | 2026-07-28 | on muskmile.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Tesla & EVs videos. Re-verify embeds. ★ Copy-paste prompt for muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site muskmile.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Tesla & EVs videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Tesla & EVs 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. | ||||
| 27 | 43 | SEO | 2026-07-28 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site muskmile.com. WHY IT MATTERS A tight internal-link web spreads authority and keeps visitors moving through the site. HOW TO APPROACH IT 1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely. 2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The change validates cleanly and the affected pages are eligible for richer results or faster discovery. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 28 | 39 | Monetize | 2026-07-31 | on muskmile.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 muskmile.com You are working on ONE specific website: muskmile.com (live at https://muskmile.com/), a Tesla & EVs site in the WholeTech network, served from /var/www/muskmile.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for muskmile.com and no other site — make all changes on muskmile.com. Act like a senior editor and web engineer who knows the Tesla & EVs niche cold. GOAL (on muskmile.com) Add the network affiliate + AdSense setup — on the site muskmile.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. | ||||