Better answers from the AI you already use.

We are working in ONE conversation. Every turn from here builds on the last. Do not restart, do not ask me to re-paste anything, and do not ask me to confirm the brief - it is below.

The brief

I want a prioritised growth plan with finished ad and page assets.

There is a standing automation that normally produces this. It is called SEO Audit Webapp, and the video that demonstrates it is titled "Build Web Apps with Firebase Studio + n8n In 30 Mins (Beginner’s Guide)". Here is what that pipeline actually does:

This system builds a SEO audit web application using Firebase Studio and a free workflow that leverages webhooks to trigger an Appify-powered audit. The setup incorporates HTTP request modules, chat agents for grouping and formatting data, and an aggregator to merge SEO metrics from multiple pages into a dynamic dashboard. Created by Jono Catliff, the blueprint is available free via the provided Gumroad link.

The original pipeline is built in n8n and wires together: n8n.

What is different about this session

That automation is a permanent pipe. I do not want the pipe. I want the output, once, produced by you working through this conversation with me over the next few turns. Do not produce an n8n JSON export, a node graph, or a workflow diagram. Produce the thing the pipe was built to produce.

Your job right now

1. Read the brief and restate the deliverable in one sentence, in your own words, so we agree on what "done" means.
2. Write a numbered execution plan - the actual production steps, in order, that you will carry out across this conversation. Be concrete: each step names an artefact it will produce.
3. List the inputs I must give you for the plan to be executable. For each one, show the exact shape you want it in, with a fill-in-the-blank template I can type over. Assume I have none of this ready.
4. Flag anything in the brief that is ambiguous or that you will have to assume. Make an explicit, defensible assumption rather than asking a vague question.
5. State the final output format you will produce in the last turn (file layout, sections, length).

Constraints for everything you produce in this conversation:
• Concrete and finished. No placeholders left where a real value belongs, no "insert your X here".
• If you cannot verify a fact, say so inline rather than inventing it.
• Every claim that rests on an external fact gets a source.
• Optimise for something I can act on this week, not for a textbook answer.

Continue from Turn 1. Do not re-plan from scratch.

Take the numbered plan you produced and turn it into a locked execution checklist:

1. Restate it as a checklist where every line is a specific artefact with a one-line definition of "finished". For example: #3 - Hook table: 10 hooks, each <= 8 words, each paired with the segment it comes from.
2. Tell me, in priority order, which inputs I must supply right now to unblock the most work. Give me a single copy-paste block with the fill-in-the-blank fields already laid out. If an input genuinely cannot be typed (a file, a link list, an API response), tell me exactly what to paste and what shape it should be.
3. Where you made an assumption in Turn 1, state it again in one line and tell me what it would cost if it is wrong. Mark each assumption as HIGH or LOW impact.
4. Tell me the order you will work in and exactly which turn each checklist item lands in, so I know what I am waiting for at each step.

Then stop and wait for my input. Do not start producing deliverables yet - I need to see the checklist first.

Continue in this same conversation. Everything below builds on Turns 1 to 2; do not restart or re-brief yourself.

Establish the ground before optimising anything.

1. Define the target: who we are trying to reach, and what they are trying to do. Narrow it until it is uncomfortable.
2. Build the keyword universe, grouped by intent - informational, commercial, transactional - and give each group's likely volume and difficulty as relative bands, not invented absolute numbers.
3. Name the competitors to study and why each is worth studying.
4. For each competitor, what they are doing that works, and where they are leaving something on the table.
5. Flag any keyword where the search intent is mismatched to what we can offer. Chasing those is the expensive mistake.

Output as a prioritisation table: keyword group | intent | why we can win | effort band.

Continue in this same conversation. Everything below builds on Turns 1 to 3; do not restart or re-brief yourself.

Rank what to actually do.

1. Score every opportunity on impact and effort, and be honest about both.
2. Produce the priority order, and say what you are deliberately not doing yet. Deferred is not the same as unlisted.
3. For the top five, state the specific change to make, in a sentence a writer or developer could act on without further research.
4. Identify the one change with the best effort-to-impact ratio, and defend that choice.
5. Give the realistic timeline, and say what would make it slip.

Output a ranked table with the reasoning visible. The reasoning is the deliverable.

Continue in this same conversation. Everything below builds on Turns 1 to 4; do not restart or re-brief yourself.

Build the assets.

1. Write the finished page copy for the top opportunity - title tag, meta description, H1, opening, and the argument structure for the body.
2. Write the ad copy for the top paid opportunity: three variants per placement, each with the angle named.
3. Write the landing page for the transactional keyword, structured for conversion, with the objections handled in-body.
4. Write the internal linking plan - which pages support which, and the anchor text.
5. For every asset, note what would make it fail.

Output finished copy, not an outline of copy.

Everything is produced. This turn is about making it one coherent thing rather than a pile of parts.

1. List every artefact produced so far in this conversation, by the name we agreed in the checklist. Flag anything from the checklist that is missing or thin.
2. Cross-check the parts against each other and report the inconsistencies you find. Be specific: which artefact says one thing and which says another. Fix them, and show the fix.
3. Rewrite the pieces that depend on each other so they use one consistent vocabulary, one consistent naming scheme, and one consistent tone. Show the corrected versions of anything you changed.
4. Identify the three weakest parts of the work and tell me honestly what would improve them. If you think something should be cut rather than polished, say so.
5. Produce a short READ ME FIRST section for the final deliverable: what this is, who it is for, how to use it, and what to do first.

Keep the README under 300 words.

Now assemble the finished a prioritised growth plan with finished ad and page assets.

1. Produce the complete deliverable in the format you committed to in Turn 1. Use every artefact from this conversation - do not start over, and do not leave anything as a note to self. This is the version I keep.
2. Run a self-check before you send it, and show the check as a short table at the end:
   • Is every checklist item from Turn 2 actually covered? List any that are not.
   • Does anything still contain a placeholder, a TODO, or an unverified claim?
   • Is the thing internally consistent - numbers, names, dates, cross-references?
   • If a real person acted on this on Monday morning, what would they trip over? Fix it.
3. Give me a NEXT 3 ACTIONS list: the three concrete things to do next, each with an owner and a timeframe. Not a wishlist - three things I can start.
4. If any part of this deliverable should be regenerated weekly or monthly, say which part and give me the single prompt that would do it, so I can reuse it.

Output the deliverable first, then the self-check table, then NEXT 3 ACTIONS.