What to do next on this site

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Build the definitive Small-Engine Repair cornerstone guide — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Small-Engine Repair 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 Small-Engine Repair — 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Lock down sensitive data — nothing private is publicly reachable — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Add an interactive tool and an email capture for Small-Engine Repair — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Small-Engine Repair (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 Small-Engine Repair — 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site alexsmallenginerepair.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 Small-Engine Repair — 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Publish: A current, data-backed explainer in Small-Engine Repair — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Trending angle in Small-Engine Repair. 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Publish: The question your Small-Engine Repair audience is searching most right now — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Trending angle in Small-Engine Repair. 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Split roles with alexsmallengine.com decisively — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Two near-identical domains cannibalize each other. Assign this one the local service-business role — the shop's site — while alexsmallengine.com carries the national how-to library, with prominent cross-links and matching canonicals. Two defined jobs beat one blurred identity duplicated; document the split in both /act/ worksheets. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Service-area pages for the local market — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Build city and county service pages — plain statements of what machines are serviced where, turnaround expectations, drop-off details — for the real coverage area only. Local small-engine searches (mower repair near me equivalents) convert to actual jobs, and honest area pages are the local-SEO backbone. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
What-we-fix equipment roster with straight answers — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Publish a plain equipment roster — walk-behinds, riders, trimmers, chainsaws, generators, tillers — with yes/no on each plus typical job types. Callers' first question is do you work on X; answering it on-page wins the visit and filters mismatched inquiries before they cost anyone time. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Publish: A 'what changed in 2026' round-up for Small-Engine Repair — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Trending angle in Small-Engine Repair. 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Drop-off intake form writing draft notifications — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Add an intake form — machine, brand, symptom, photo upload, phone — that writes a Gmail DRAFT for review, never auto-sending. Pre-qualified intake turns website visits into scheduled bench work and lets busy periods queue jobs instead of losing calls that ring out. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Tune-up season packages with clear flat pricing — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Offer named flat-rate packages — spring mower tune-up, generator readiness check — listing exactly what each includes (plug, oil, blade, carb inspection). Flat packages presell routine work, smooth seasonal cashflow, and give every seasonal page a concrete bookable offer instead of a vague call-us. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Deepen the main Small-Engine Repair guide with current data and examples — on the site alexsmallenginerepair.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 Small-Engine Repair 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 Small-Engine Repair.
- 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
DIY-or-pro fork linking sibling site's parts lists — on the site alexsmallenginerepair.com.

WHY IT MATTERS
On each service page, add an honest fix-it-yourself fork linking the matching alexsmallengine.com guide with its colinfirthfan-20 parts list. DIY-leaning visitors monetize through affiliate parts instead of bouncing; service-leaning ones stay. Both outcomes pay, and the candor builds the local reputation. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Workbench realism: pegboard, tool silhouettes, oil-rag texture — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Art-direct as the actual shop — pegboard backgrounds with hanging-tool silhouettes framing sections, worn oil-rag texture on panels, machined-metal buttons, and a shop-hours sign rendered like hand-painted signage. It should feel like walking up to a trusted local bench, not a franchise template. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Job-ticket styling for services and pricing — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Present each service package as a carbon-copy repair ticket — perforated edge, handwritten-style fields, stamped price box. The repair-ticket idiom is universally understood at a glance, keeps pricing feeling concrete and honest, and gives the site a signature card style screenshots preserve. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Add an FAQ answering the top questions in Small-Engine Repair — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Pull the real questions people ask in Small-Engine Repair and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Small-Engine Repair 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 Small-Engine Repair.
- 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Season-opening announcement via newsletter widget — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Use wholetech.com/newsletter/widget.js for a strictly local list — two or three sends a year announcing spring rush booking and fall generator checks. Local customers forget the shop between seasons; a tiny honest list converts last year's customers into this year's first bookings. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
LocalBusiness schema with services and hours — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Add LocalBusiness JSON-LD — service area, hours, offerings as Service entries — plus FAQ schema for do you fix chainsaws and how long does mower repair take. Two sitemaps, IndexNow, af-deploy.py to 90+. Near-me answers are agent territory now; structured local data wins them. (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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Keep the live / news feed updated on cadence (2×/day) — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Small-Engine Repair items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Small-Engine Repair: 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 Small-Engine Repair 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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Add Article + FAQ structured data — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Add the network affiliate + AdSense setup — on the site alexsmallenginerepair.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.

You are working on ONE specific website: alexsmallenginerepair.com (live at https://alexsmallenginerepair.com/), a Small-Engine Repair site in the WholeTech network, served from /var/www/alexsmallenginerepair.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for alexsmallenginerepair.com and no other site — make all changes on alexsmallenginerepair.com. Act like a senior editor and web engineer who knows the Small-Engine Repair niche cold.

GOAL (on alexsmallenginerepair.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site alexsmallenginerepair.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Small-Engine Repair videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Small-Engine Repair 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.