Choose one visible asset
Use one post, one carousel, one ad, one profile surface, or one product page. Mixed audits create vague fixes.
Free static worksheet
Use this when a post, reel, carousel, ad, profile, or product page underperforms and you need to find the first visible bottleneck before rewriting everything.
This is not an algorithm checklist. It is a reader-path checklist: what did the viewer understand, where did trust leak, and which next action became unclear?
After downloading, start with one asset. Mark the first break, then open the matching lab below instead of auditing the whole account at once.
How to use it
Start by asking what the next person in the path could understand. Good taste can still hide a weak promise, a late proof point, or a CTA that asks for action before trust exists.
Use one post, one carousel, one ad, one profile surface, or one product page. Mixed audits create vague fixes.
Find the earliest place where the viewer has to guess the audience, promise, proof, or next action.
Rewrite the smallest surface that controls the break. Most tests get noisy when you change the hook, body, CTA, and profile at once.
Compare assets that had the same job. A save post, a share post, a follow post, and a sales post should not be judged by one metric.
First diagnosis routes
After the 12-minute pass, open the model that matches the earliest visible break. This keeps the audit from turning into a full-account rewrite.
Check whether the first audience created enough evidence for a stranger to understand the promise, not whether the topic deserved more reach in theory.
Check the first visible promise, visual contrast, and opening sentence before rewriting the whole body.
Separate quick approval from future-use intent, then match the desired signal to the job of the post.
Compare the promise, click intent, landing-page proof, price expectation, and purchase path before blaming traffic quality.
Compare the promise, first visual, audience self-selection, click intent, and landing-page handoff before copying the winner.
Trace attention, click intent, trust, product clarity, price pressure, and purchase effort as separate stages.
Check whether the free step introduces the paid problem, builds trust, and leaves a reason to continue.
Open the profile from the post that caused the visit and check whether the first screen repeats the same promise in account language.
Check whether the first test group can classify the post quickly enough to justify a wider second pass.
Check whether the first three seconds prove the payoff is coming, not just whether the later explanation is useful.
Check whether the saved item points back to a repeatable account promise or only solves one isolated problem.
Check whether low cost brings the right reader, not only whether the auction looks efficient.
Check whether the first images answer what it is, who it helps, proof it works, and what happens after purchase.
Check whether the bio names the reader, useful outcome, and next step in one tight path.
Check whether the post gives the system and the reader the same category signal from the first visible cue.
Check whether the hook states the reader problem before the useful insight appears.
Check whether the comments add clarity, trust, or distribution intent instead of low-context noise.
Check whether the landing page repeats the same promise, proof, and next action the ad created.
Check clarity, fit, and trust separately instead of treating hesitation as one vague conversion problem.
Check whether the menu asks for too many decisions before the visitor sees the strongest next action.
Check whether the post creates future-account expectation, not only a finished one-post moment.
Check how many seconds pass before the viewer sees the consequence, contrast, or payoff.
Check whether pinned posts explain the account promise, proof, and best starting point faster than the full grid.
Check whether the discussion builds trust or only creates friction around the account promise.
Entry signal
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Meaning signal
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Action signal
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Trust signal
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Answer with a specific asset detail, not a general opinion. If the answer is "maybe," that is the bottleneck to test first.
Repair menu
The fastest useful test is usually a small repair on the earliest visible break. Use one of these passes before changing the whole strategy.
Change only the first line, cover, or first frame. Keep the body stable so you can learn whether entry clarity was the issue.
If viewers leave before the useful part appears, pull a result, example, contrast, or real-use image into the first visible moment.
Use the same problem language across post, profile, landing page, and CTA. Many leaks start when each surface says something slightly different.
Remove the slide, intro, image, or menu choice that looks polished but does not help the reader decide.
Before broadening the topic, name the adjacent audience that would understand the post next.
For ads and funnels, judge the creative by qualified intent, not only low-cost traffic, low CPM, or surface curiosity.
Follow-up labs
The audit sheet is the fast pass. The visual labs show the shape of the problem with motion so the diagnosis becomes easier to remember.
Use this when a post got a first audience but failed to earn a wider test.
Use this when followers understood the post, but colder viewers did not get the context quickly enough.
Use this when the useful idea exists, but the first line or frame does not make it worth entering.
Use this when the best part of the post arrives too late for viewers to reach it.
Use this when slide one gets attention but does not earn the next swipe.
Use this when people may approve of the post, but cannot see a future moment for using it again.
Use this when the post is useful as a one-off reference but does not explain why the account deserves future attention.
Use this when curiosity reaches the profile, but the bio, grid, or pinned posts do not create a follow expectation.
Use this when delivery concentrates around one creative and you need to inspect why that path gave clearer evidence.
Use this when the ad earns curiosity but the landing page does not continue the same promise.
Use this when a download creates collectors but does not preview the paid workflow or buying reason.
Use this when the product looks good but the buyer still cannot answer fit, proof, use, or risk.
Use this when traffic exists, but the buyer path narrows before decision quality appears.
Use this when posts look polished in isolation but do not leave a repeatable account memory.
This worksheet uses simplified conceptual models. It does not reproduce any private ranking, recommendation, or advertising system. Real platforms use many more signals, and those systems change over time.