◆ Google Looker

Perform on-page SEO and website health 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 taskGenerate a website health report for the new product launch pages, focusing on broken links and…+
Generate a website health report for the new product launch pages, focusing on broken links and page load times, and share it with the web development team by 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 launch the new campaign, run an audit on the landing pages. Don't just list technical…+
Before we launch the new campaign, run an audit on the landing pages. Don't just list technical issues; prioritize them by their potential impact on conversion rates and flag anything that would make a user abandon the page.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe web development team just finished a huge site migration, and I'm nervous about new…+
The web dev team just pushed a major site update, and I'm worried about new technical SEO issues, but I don't know where to focus first to check for problems.
The web development team just finished a huge site migration, and I'm nervous about new technical SEO issues. I need to do an audit, but I'm overwhelmed by where to start. What are the top three critical areas to check immediately that could break our search visibility, and what's the fastest way to get a clear picture for Sarah in marketing?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time the development team deploys a new feature or makes a site change, I spend hours…+
I spend too much time manually checking for website health issues after every development push, often missing critical problems until they impact performance.
Every time the development team deploys a new feature or makes a site change, I spend hours manually checking for website health issues. I often miss critical problems that only surface later. What habit should I change to more efficiently and reliably catch these technical SEO issues before they impact our organic traffic?
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 Google Looker'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.