◆ JavaScript

Perform on-page SEO audits

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun an SEO audit on the new product page for the 'Quantum Leap' smartwatch. Check for broken…+
Run an SEO audit on the new product page for the 'Quantum Leap' smartwatch. Check for broken links, image alt-text, and meta descriptions, and give me a list of critical fixes needed before it launches on Tuesday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we push the new blog post about 'AI in Healthcare' live, perform an on-page SEO review.…+
Before we push the new blog post about 'AI in Healthcare' live, perform an on-page SEO review. Focus on keyword density for 'AI healthcare solutions,' readability for a medical professional audience, and internal linking opportunities to our existing whitepapers, so it ranks well.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur competitor's new landing page for 'Secure Cloud Storage' just outranked ours for our…+
Our competitor's new landing page for 'Secure Cloud Storage' just outranked ours for our primary keyword.
Our competitor's new landing page for 'Secure Cloud Storage' just outranked ours for our primary keyword, and I'm worried about losing market share. I don't know if their content is just better, or if they've found a technical exploit. What's the most critical thing to check on our page right now to understand why we dropped?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself making small, reactive SEO fixes after a page has already launched, which…+
I often find myself making small, reactive SEO fixes after a page has already launched.
I often find myself making small, reactive SEO fixes after a page has already launched, which feels like playing catch-up. This happens with almost every new content piece. What habit can I change to integrate proactive on-page SEO checks earlier into the content creation workflow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.