SOP 3: Shopify App Review Content Research and Brief Creation

SOP Information

1. Purpose

The purpose of this SOP is to define how Blinto converts completed Shopify app research and testing into a clear, evidence-based, SEO-focused content brief.

The content brief must give the writer everything required to produce a useful and trustworthy article without repeating the app research or guessing what should be included.

The process ensures that every Shopify app review:

• Satisfies a clear search intent.
• Targets relevant keywords naturally.
• Answers real merchant questions.
• Uses findings from hands-on testing.
• Covers important Shopify app entities and concepts.
• Provides more value than existing competing content.
• Connects with Blinto’s Shopify services.
• Supports the wider Shopify app content cluster.
• Includes clear writing, evidence, visual, and quality requirements.

This SOP must be completed before writing begins.

2. SOP Objective

This SOP helps Blinto:

• Define the correct search intent for each article.
• Identify primary and secondary keywords.
• Analyze current competing content.
• Find meaningful content gaps.
• Build a differentiated review angle.
• Organize research into a logical outline.
• Maintain semantic and topical relevance.
• Map research evidence to the correct sections.
• Plan internal links and calls to action.
• Give writers clear instructions.
• Reduce unnecessary revisions.
• Maintain consistency across all Shopify app review content.
• Build connected content clusters instead of isolated articles.

3. Scope

This SOP covers:

• Reviewing the approved app-research handoff
• Defining the audience and merchant problem
• Search-intent analysis
• Keyword research
• Search-result and competitor analysis
• Content-gap identification
• Content-angle development
• Entity and semantic-topic mapping
• User-question research
• Outline creation
• Evidence placement
• Internal-link planning
• CTA planning
• Visual-content requirements
• Metadata recommendations
• Writer instructions
• Content-brief quality assurance
• Content-brief approval
• ClickUp updates and handoff

This SOP does not cover:

• App installation or testing
• App scoring
• Writing the full article
• Editorial revisions
• Graphic design production
• Publishing
• Founder outreach
• Content performance tracking

These activities are covered in separate SOPs.

4. Entry Requirements

SOP 3 begins only when:

• SOP 2 has been completed.
• The app research has been approved.
• The ClickUp task status is Research Completed.
• The app-testing level is documented.
• Pricing, features, integrations, and merchant feedback have been researched.
• Screenshots and supporting evidence are organized.
• Technical findings have been validated.
• The app-scoring framework is complete.
• Best-fit and poor-fit merchants have been identified.
• The app research handoff summary is attached.
• The assigned SEO Strategist or Content Strategist is confirmed.

The content strategist must not create the final brief from incomplete or unapproved research.

5. Expected Output

At the end of this SOP, the team must have:

1. A confirmed target audience.
2. A clearly defined merchant problem.
3. A confirmed primary search intent.
4. A selected content format.
5. A primary keyword.
6. Relevant secondary and semantic keywords.
7. A completed competitor-content analysis.
8. A documented content-gap analysis.
9. A differentiated content angle.
10. A mapped list of important entities and concepts.
11. A complete H1, H2, and H3 outline.
12. Section-level writing instructions.
13. Research evidence mapped to relevant sections.
14. An internal-linking plan.
15. A CTA and conversion plan.
16. Recommended visual requirements.
17. Suggested title tag and meta description.
18. Required disclosures and trust signals.
19. A complete writer-ready content brief.
20. An approved ClickUp status of Brief Approved.

6. Roles and Responsibilities

One person may perform both the SEO Strategist and Content Strategist roles during the validation phase.

7. Required Tools and Resources

The team may use:

• Approved app-research document
• Shopify App Store
• Official app website and documentation
• Google Search
• Google Search Console
• Google Analytics
• Ahrefs, Semrush, or another keyword-research platform
• Google Trends where relevant
• Google Sheets or Airtable
• ClickUp
• Blinto’s Shopify App Knowledge Base
• Blinto website sitemap
• Existing Shopify content inventory
• Competitor-content analysis template
• Content-brief template
• Internal-linking worksheet

Research must rely on approved evidence and reliable sources.

8. Required Templates

The following templates should be available:

• Shopify App Review Content Brief Template
• Keyword Research Sheet
• Search Intent Analysis Template
• Competitor Content Comparison Sheet
• Content Gap Analysis Template
• Entity and Semantic Coverage Sheet
• User Question Research Sheet
• Internal Linking Plan
• Evidence Mapping Table
• Visual Recommendation Sheet
• Content Brief QA Checklist
• Brief Approval Checklist

9. Complete Content Research and Brief Creation Workflow

Step 1: Review the Approved Research Handoff

The SEO Strategist must first review the complete output from SOP 2.

Review:

• App or category name
• Content format
• Testing level
• Core merchant problem
• Best-fit merchant
• Poor-fit merchant
• Main features
• Important limitations
• Pricing observations
• Installation experience
• Onboarding findings
• Merchant-feedback patterns
• Integrations
• Support findings
• Technical notes
• App score
• Differentiators
• Relevant alternatives
• Screenshots and evidence
• Claims that must not be made
• Required disclosures

Questions to Answer

• Is the research complete enough to support the planned content?
• Are any important facts missing?
• Does the evidence support a strong verdict?
• Are there any technical or legal wording limitations?
• Does the app-testing level affect how the content must be written?
• Is the original topic still appropriate after testing?

Possible Decisions

Output

A confirmed research base for the content brief.

Step 2: Confirm the Content Format

Confirm whether the article will be:

• Category or bulk review
• Single app review
• App comparison article

The format approved in SOP 1 may be changed if hands-on research reveals that another format would better serve the user.

Example

A planned single app review may become a comparison article if:

• The app has very low branded search demand.
• Merchants primarily compare it with another app.
• The research does not support enough depth for a standalone article.
• A direct competitor provides a stronger decision-making context.

Any format change must be approved and recorded in ClickUp.

Step 3: Define the Target Audience

The content brief must define exactly who the article is for.

Possible audiences include:

• New Shopify merchants
• Small Shopify store owners
• Growing DTC brands
• High-volume merchants
• Shopify Plus merchants
• Dropshipping businesses
• Subscription businesses
• B2B Shopify merchants
• International sellers
• Shopify agencies
• Shopify developers
• Ecommerce managers
• Marketing teams
• App founders researching competitors

Audience Profile Requirements

Document:

• Merchant type
• Store size
• Growth stage
• Technical skill level
• Main problem
• Budget sensitivity
• Required features
• Main decision concerns
• Current alternatives
• Desired outcome

Example

Target audience:
Small and growing Shopify merchants looking for an affordable product review app that is easy to install and does not require advanced technical knowledge.

Step 4: Define the Merchant Problem

Every content brief must identify the merchant problem behind the search.

Examples:

• The merchant does not know which app is best for a particular use case.
• The merchant wants to know whether one app is worth the cost.
• The merchant is comparing two similar apps.
• The merchant is concerned about setup difficulty.
• The merchant needs an app that works with an existing technology stack.
• The merchant is trying to avoid performance or compatibility problems.
• The merchant needs a solution that can scale with store growth.

Required Statement

Complete this sentence:

The reader needs this content because they are trying to decide whether [app or category] can help them [specific merchant goal] without creating [main concern or limitation].

This statement should guide the entire brief.

Step 5: Define the Search Intent

The SEO Strategist must identify the primary and secondary search intent.

Main Search Intent by Content Type

Additional Intent Types

The reader may also want to understand:

• Pricing
• Features
• Ease of use
• Setup requirements
• Integrations
• Merchant suitability
• Limitations
• Alternatives
• Support quality
• Performance impact
• Scalability
• Free-plan availability
• Best app by use case

Search Intent Summary

The brief must include:

• Primary intent
• Secondary intent
• Reader decision stage
• Main decision the reader needs to make
• Information required before the reader can decide

Step 6: Conduct Keyword Research

The SEO Strategist must research keywords that match the approved topic and search intent.

Keyword Types

Primary Keyword

The main query the article should satisfy.

Examples:

• Best Shopify review apps
• Judge.me review
• Judge.me vs Loox
• Best Shopify apps for dropshipping

Secondary Keywords

Closely related queries that support the main topic.

Examples:

• Judge.me pricing
• Judge.me features
• Is Judge.me free?
• Judge.me alternatives
• Judge.me Shopify review
• Judge.me pros and cons

Semantic Keywords and Concepts

Related terms that help explain the subject naturally.

Examples:

• Product reviews
• User-generated content
• Photo reviews
• Review widgets
• Review requests
• Google Shopping reviews
• Review moderation
• Shopify integrations
• Review imports
• Store conversion

Long-Tail Keywords

Specific questions or use cases.

Examples:

• Is Judge.me good for small Shopify stores?
• Does Judge.me slow down Shopify stores?
• Can Judge.me import reviews?
• Judge.me vs Loox for photo reviews
• Best Shopify review app for beginners

Keyword Evaluation Criteria

Evaluate:

• Search intent
• Relevance
• Search demand
• Ranking difficulty
• Existing website authority
• Search-result quality
• Commercial relevance
• Long-tail opportunity
• Connection to Blinto’s services
• Ability to answer the query with available evidence

Important Rule

Do not choose a keyword only because it has higher search volume.

The primary keyword must accurately match the article’s content and user intent.

Step 7: Create the Keyword Map

The brief should include a keyword map.

Keywords should not be assigned to sections where they do not fit naturally.

Step 8: Analyze the Search Results

Review the current search results for the primary keyword.

Analyze:

• Ranking page types
• Content format
• Titles
• Heading structures
• Word-count ranges
• Featured snippets
• Comparison tables
• Review dates
• Author information
• Testing claims
• Screenshots
• Videos
• FAQs
• App founder content
• Affiliate content
• Independent review content
• User-generated discussions
• Shopify App Store results
• Alternative and comparison pages

Search Result Questions

• What type of content currently ranks?
• What does Google appear to consider relevant?
• Are results mostly independent or affiliate-driven?
• Do competitors provide real testing evidence?
• Are results outdated?
• Are verdicts clear?
• Are merchant use cases explained?
• Are important limitations missing?
• Is there room for a more practical review?

Output

A short search-result summary explaining what the article must do to compete.

Step 9: Select Content Competitors

Select approximately:

• 3–5 direct competitors for a single app review
• 4–6 competitors for a category review
• 3–5 competitors for a comparison article

Choose pages that:

• Target the same or highly similar intent.
• Currently rank or appear highly relevant.
• Represent different content approaches.
• Include at least one strong independent source where possible.
• Include the official app or product source where useful.

Do not select competitors only because they have long content.

Step 10: Complete Competitor Content Analysis

For each selected competitor, record:

Important Rule

Competitor analysis should help Blinto create better content. It should not be used to copy headings, language, opinions, or conclusions.

Step 11: Identify Content Gaps

Content gaps should be based on merchant usefulness, not only missing keywords.

Possible Gaps

• No hands-on testing
• No clear testing methodology
• Outdated pricing
• Missing app limitations
• Weak merchant-fit explanation
• No poor-fit merchant guidance
• No technical validation
• No setup screenshots
• No onboarding evaluation
• No direct feature testing
• No performance discussion
• No integration details
• No support evaluation
• No recent merchant-feedback patterns
• No meaningful alternatives
• Weak final verdict
• Generic pros and cons
• No comparison by use case
• No explanation of pricing at scale
• No disclosure of testing limitations
• No distinction between public claims and observed findings

Gap Prioritization

Prioritize gaps that:

• Help merchants make better decisions.
• Are supported by Blinto’s research.
• Demonstrate real expertise.
• Differentiate Blinto from generic affiliate content.
• Connect with Blinto’s Shopify services.

Step 12: Define the Content Angle

The content angle is the main perspective that makes the article useful and different.

Strong Content Angles

• Best option for a specific merchant type
• Practical review based on setup and testing
• Honest evaluation of value at different growth stages
• Comparison based on real merchant workflows
• Review focused on ease of use for beginners
• Review focused on scalability for growing stores
• Comparison focused on pricing versus feature depth
• Evaluation based on app-stack compatibility
• Review focused on implementation and maintenance requirements

Required Content Angle Statement

Complete:

This content will help [target audience] decide [specific decision] by evaluating [main criteria] using [testing, research, or comparison evidence].

Example

This content will help small and growing Shopify merchants decide whether Judge.me is the right product review app by evaluating its installation, pricing, customization, review-collection features, and limitations through hands-on testing and recent merchant feedback.

Step 13: Define the Unique Value Proposition

The brief must explain why the Blinto article deserves to exist.

Possible unique value includes:

• First-hand installation and testing
• Clear test methodology
• App screenshots
• Merchant-fit recommendations
• Poor-fit guidance
• Technical validation
• Pricing analysis by store size
• Use-case-specific recommendations
• Balanced merchant-feedback analysis
• Comparison using consistent criteria
• Clear disclosure of untested features
• Expert Shopify perspective
• Integration and implementation guidance

Required Statement

Unlike generic app summaries, this article will provide [specific evidence or perspective] so merchants can [specific decision or outcome].

Step 14: Map Primary Entities

Every brief must identify important entities that should be covered naturally.

Primary Entities

These are central to the article.

Examples:

• App name
• App developer
• Shopify
• Shopify App Store
• Main app category
• Direct competitor apps
• Main integration platforms
• Shopify plans where relevant

Secondary Entities

These support understanding.

Examples:

• Product reviews
• User-generated content
• Subscriptions
• Upsells
• Dropshipping suppliers
• Email automation
• Shopify Flow
• Theme app extensions
• Checkout Extensibility
• Google Shopping
• Klaviyo
• Recharge
• PageFly
• Online Store 2.0

Entity Rules

• Mention entities only when relevant.
• Explain the relationship between entities.
• Do not insert app names only for SEO.
• Use the correct product and company names.
• Confirm technical terms before adding them to the brief.

Step 15: Build the Semantic Topic Map

The semantic topic map should identify the concepts required to answer the search intent completely.

Example for a Single App Review

• What the app is
• Core use case
• Installation
• Onboarding
• Features
• Pricing
• Customization
• Integrations
• Merchant suitability
• Limitations
• Support
• Alternatives
• Final verdict

Example for a Category Review

• Category definition
• Merchant problem
• Selection criteria
• Best apps by use case
• Feature differences
• Pricing models
• Integration needs
• Store-size suitability
• Implementation considerations
• Final recommendations

Example for a Comparison

• Core use cases
• Feature differences
• Pricing differences
• Setup
• Ease of use
• Customization
• Integrations
• Support
• Scalability
• Winner by use case
• Final decision

The semantic map should help the article answer the topic completely without becoming unnecessarily broad.

Step 16: Research User Questions

Collect questions that merchants may ask before selecting the app.

Possible sources include:

• Search suggestions
• People Also Ask
• Related searches
• App Store reviews
• Community discussions
• Support documentation
• Competitor FAQs
• Sales or support conversations
• Internal Shopify expertise

Question Categories

• What is the app?
• How does it work?
• Is it free?
• How much does it cost?
• Is it easy to install?
• Does it require coding?
• Which Shopify plans support it?
• Does it affect store speed?
• Which integrations does it support?
• Is it suitable for small stores?
• Can it scale?
• What are its limitations?
• What are the best alternatives?
• Which app is better?
• Can it be removed safely?

Question Selection Rule

Include questions that:

• Match the search intent.
• Affect the buying or installation decision.
• Can be answered with evidence.
• Are not already answered clearly in the main body.

Avoid creating a long FAQ section only to target keywords.

Step 17: Map Evidence to Content Sections

The strategist must connect research evidence with the outline.

Evidence Labels

Use:

• Tested by Blinto
• Partially tested
• Verified through official documentation
• Reported by merchants
• Not tested
• Technical review required

This helps the writer describe evidence accurately.

10. Content Structure Requirements

A. Category or Bulk Review Brief

Recommended H1

Best Shopify [Category] Apps for [Merchant Use Case or Year, if relevant]

Required Sections

1. Introduction
2. Quick recommendation summary
3. Comparison table
4. How Blinto selected and evaluated the apps
5. Best app by use case
6. Individual app evaluations
7. Pricing comparison
8. Feature comparison
9. How to choose the right app
10. Implementation considerations
11. Final recommendation
12. FAQ
13. Blinto CTA

Each App Section Should Include

• What the app does
• Best for
• Main strengths
• Important limitation
• Pricing summary
• Testing level
• Why it was included
• Brief verdict

Category Article Rule

Do not give all apps equal positioning.

The brief must clearly identify:

• Best overall
• Best for beginners
• Best value
• Best for advanced stores
• Best for a specific merchant type
• Best free option, where appropriate

Recommendations must be supported by evidence.

B. Single App Review Brief

Recommended H1

[App Name] Review: Is It Right for Your Shopify Store?

Required Sections

1. Introduction
2. Quick verdict
3. Review methodology and testing disclosure
4. What is [App Name]?
5. Who is it best for?
6. Key features
7. Installation and onboarding
8. Ease of use
9. Pricing and value
10. Integrations
11. Merchant-feedback patterns
12. Pros and cons
13. Important limitations
14. Alternatives
15. Final verdict
16. FAQ
17. Blinto CTA

Single Review Rule

The outline must provide enough depth to justify a standalone article.

Do not create a separate heading for every small feature.

Group related features based on merchant use cases.

C. Comparison Article Brief

Recommended H1

[App A] vs [App B]: Which Shopify App Is Better?

Required Sections

1. Introduction
2. Quick verdict
3. Side-by-side comparison table
4. Who each app is best for
5. Feature comparison
6. Installation and onboarding
7. Ease of use
8. Pricing and value
9. Customization
10. Integrations
11. Support and documentation
12. Scalability
13. Pros and cons of each
14. Winner by use case
15. Final recommendation
16. FAQ
17. Blinto CTA

Comparison Rule

Use the same evaluation criteria for both apps.

The final verdict should identify:

• When App A is better
• When App B is better
• Which app is best for specific merchant types
• Whether there is a clear overall winner

Avoid forcing a universal winner when both apps serve different users.

11. Create the Detailed Heading Outline

The content strategist must create a complete H1, H2, and H3 structure.

For every heading, include:

• Heading title
• Purpose
• Search intent satisfied
• Key discussion points
• Questions to answer
• Important entities
• Evidence to use
• Suggested word allocation
• Internal-link opportunity
• Visual requirement
• Writer notes

Example Section Instruction

H2: Judge.me Pricing and Value

Purpose:
Explain how Judge.me pricing works and whether it provides good value for different merchant sizes.

Questions to answer:

• Is there a free plan?
• Which features are included?
• What does the paid plan add?
• Are there usage limits?
• Which merchants receive the best value?

Evidence:

• Official pricing page checked on [date]
• Hands-on feature-access notes
• Merchant feedback about pricing

Writer note:
Do not describe the app as cheap without explaining the included features and merchant context.

12. Define the Direct Answer Strategy

Important questions should receive clear answers early.

Examples:

• Is the app worth using?
• Who is it best for?
• How much does it cost?
• Which app is better?
• Does the app require coding?
• What is the best option in the category?

Direct Answer Rules

• Answer the main query in the introduction or quick verdict.
• Avoid delaying the verdict until the conclusion.
• Add context after the direct answer.
• Use clear wording.
• Do not make stronger claims than the evidence supports.
• Mention important limitations near the recommendation.

13. Plan the Introduction

The brief should tell the writer how to open the article.

Introduction Requirements

The introduction should:

• Identify the merchant problem.
• State what the app or category does.
• Explain what was researched or tested.
• Preview the decision the article will help with.
• Avoid a long general explanation of Shopify.
• Avoid unsupported statistics.
• Avoid generic ecommerce introductions.

Suggested Introduction Flow

1. Merchant problem
2. App or category relevance
3. Blinto’s testing or research approach
4. Clear article promise

14. Plan the Quick Verdict

Every app review and comparison article should include a concise verdict near the beginning.

Quick Verdict Requirements

Include:

• Overall recommendation
• Best-fit merchant
• Main strength
• Main limitation
• Testing level where relevant

Example Format

Quick verdict:
[App] is a strong option for [merchant type] that needs [main use case]. Its strongest advantage is [strength], but merchants that require [missing need] may prefer an alternative.

The verdict must reflect the completed app research.

15. Plan the Comparison Table

Category and comparison articles should usually include a table.

Possible Table Columns

For category reviews:

• App
• Best for
• Starting price
• Free plan
• Main strength
• Main limitation
• Overall score

For comparisons:

• Criteria
• App A
• App B
• Winner

Table Rules

• Keep information concise.
• Verify all pricing.
• Use consistent criteria.
• Avoid overcrowding.
• Explain important details in the body.
• Include the pricing verification date where appropriate.
• Do not place unsupported scores in the table.

16. Plan Pros and Cons

Pros and cons must come from evidence.

Good Pros and Cons

• Specific
• Merchant-focused
• Supported by testing
• Relevant to purchase or installation decisions
• Balanced

Weak Pros and Cons

• “Easy to use”
• “Great features”
• “Good support”
• “Can be expensive”

These should be made more specific.

Better Examples

• Guided onboarding made the first review-widget setup possible without code.
• Advanced customization requires the paid plan.
• Pricing remains predictable for small stores but may offer less value for merchants that only need basic review collection.

17. Plan the Final Verdict

The brief should define what the conclusion must decide.

Final Verdict Must Include

• Who should choose the app
• Who should avoid it
• Main reason to select it
• Main limitation
• Best alternative where relevant
• Clear final recommendation
• No new information

The conclusion should not simply repeat the introduction.

18. Develop the Internal Linking Plan

Every brief must include internal-link recommendations.

Link Types

Parent or Category Link

Example:

A Judge.me review links to Best Shopify Review Apps.

Supporting Review Links

Example:

A category article links to Judge.me, Loox, and Yotpo reviews.

Comparison Links

Example:

Judge.me Review links to Judge.me vs Loox.

Educational Links

Example:

• How to Choose a Shopify Review App
• How Shopify Apps Affect Store Performance

Service Links

Relevant Blinto services may include:

• Shopify App Development
• Shopify App Marketing
• Shopify App Support and Maintenance
• Shopify Store Development
• Shopify Integration Services
• Shopify Conversion Optimization

Internal Linking Requirements

For each suggested link, include:

• Target page
• Recommended source section
• Suggested anchor-text direction
• Purpose of the link
• Existing or planned status

Important Rule

Do not force links to unrelated Blinto services.

The link must help the reader continue their journey.

19. Plan the CTA

The CTA should connect the merchant’s need with a relevant Blinto service.

Possible CTA Objectives

• Request Shopify app setup support
• Discuss Shopify app development
• Improve an existing Shopify app
• Get help choosing an app stack
• Request integration support
• Improve Shopify app marketing
• Resolve app performance or compatibility issues

CTA Requirements

The brief must define:

• CTA goal
• Target audience
• Relevant service
• CTA placement
• Primary CTA text direction
• Supporting copy direction

Recommended CTA Placements

• Soft contextual CTA in the body where relevant
• Main CTA after the final verdict

Example

Need help selecting or integrating the right Shopify apps? Blinto can evaluate your store requirements, configure your app stack, and support custom Shopify integrations.

Avoid aggressive sales language that weakens editorial trust.

20. Define Visual Requirements

The brief should identify visuals that improve understanding.

Possible Visuals

• Featured image
• App dashboard screenshots
• Installation screenshots
• Setup workflow
• Storefront result
• Mobile result
• Feature comparison table
• Pricing comparison table
• Pros and cons cards
• App-selection flowchart
• Best-app-by-use-case graphic
• Scoring summary
• Integration diagram

Visual Requirement Fields

For each visual, include:

• Visual type
• Section placement
• Purpose
• Source
• Required caption
• Suggested alt text direction
• Whether the visual is publishable
• Whether private data must be removed

Do not add visuals only for decoration.

21. Define Trust and Experience Signals

Every brief must tell the writer how to demonstrate credibility.

Required Trust Signals

Where relevant:

• Explain Blinto’s testing methodology.
• State the testing level.
• Mention when the app was tested.
• Record when pricing was verified.
• Use original screenshots.
• Separate tested findings from merchant-reported experiences.
• Mention technical validation where relevant.
• Disclose untested features.
• Include an author or reviewer with relevant Shopify expertise.
• Include a last-updated date.
• Disclose sponsorships, partnerships, or affiliate relationships.

Important Rule

Do not describe the content as independent if a commercial relationship affected the review process.

Editorial control must remain with Blinto.

22. Define Writing Style and Tone

The content should be:

• Practical
• Honest
• Merchant-focused
• Clear
• Confident but not exaggerated
• Evidence-based
• Balanced
• Easy to scan
• Helpful to both technical and non-technical readers

Writing Rules

The writer should:

• Use active voice.
• Use short paragraphs.
• Explain technical terms.
• Give direct answers.
• Use examples where helpful.
• Explain why features matter.
• Connect observations to merchant outcomes.
• Mention limitations clearly.
• Avoid keyword stuffing.
• Avoid generic promotional claims.
• Avoid robotic transitions.
• Avoid repeating the same point in several sections.
• Avoid copying app marketing language.

23. Define Claims and Wording Restrictions

The brief must identify any claims that require caution.

Claims Requiring Strong Evidence

• The app increases sales.
• The app improves conversion rates.
• The app is the best in the category.
• The app does not affect store speed.
• The app is completely secure.
• The app works with every theme.
• The app has excellent support.
• The app is suitable for every Shopify store.
• The app is cheaper than all competitors.

Safer Wording

Instead of:

This app will increase conversions.

Use:

The app provides features designed to support conversion-focused offers, but results will depend on the store, offer strategy, and implementation.

The brief should list any unsupported claims that the writer must avoid.

24. Define Recommended Content Length

Word count should be based on topic complexity, not competitor length alone.

General Guidance

These are planning ranges, not strict requirements.

The content should be long enough to satisfy the search intent without repetition or filler.

25. Create the Final Content Brief

The final content brief must include the following sections.

A. Content Overview

• Final working title
• Content type
• App category
• Primary keyword
• Secondary keywords
• Search intent
• Target audience
• Merchant problem
• Reader decision stage
• Content goal
• Business goal

B. Research Summary

• Testing level
• Research date
• Main findings
• Best-fit merchant
• Poor-fit merchant
• Strengths
• Limitations
• Pricing summary
• App score
• Technical notes
• Required disclosures

C. Search and Competitor Findings

• Search-result summary
• Selected competitors
• Competitor strengths
• Competitor weaknesses
• Missing topics
• Differentiation opportunity

D. Semantic SEO Foundation

• Primary entities
• Secondary entities
• Related concepts
• Important terminology
• Keyword map
• User questions
• Semantic relationships

E. Content Angle

• Main angle
• Unique value proposition
• Direct-answer strategy
• Core recommendation direction

F. Detailed Outline

For each H2 and H3:

• Heading
• Purpose
• Search intent
• Key discussion points
• Questions to answer
• Evidence
• Entities
• Internal links
• Visuals
• Writer instructions
• Suggested length

G. Conversion Plan

• CTA goal
• Relevant Blinto service
• CTA placement
• CTA copy direction
• Supporting conversion path

H. Trust Requirements

• Testing disclosure
• Pricing verification date
• Technical reviewer
• Screenshot requirements
• Partnership disclosure
• Claims to avoid

I. Metadata

• Suggested title tag
• Suggested meta description
• Suggested URL slug
• Suggested featured-image concept
• Suggested image alt-text direction

J. Final Instructions

• Tone
• Style
• Formatting
• Word-count guidance
• Required tables
• Required visuals
• Required links
• Required disclosures
• Definition of complete

26. Metadata Requirements

Title Tag

The title tag should:

• Match search intent.
• Include the primary keyword naturally.
• Communicate the article’s value.
• Avoid misleading claims.
• Remain readable.

Meta Description

The meta description should:

• Summarize what the reader will learn.
• Mention the main decision or comparison.
• Include the primary keyword naturally where possible.
• Avoid unsupported promotional claims.

URL Slug

Keep the URL:

• Short
• Descriptive
• Lowercase
• Free from unnecessary words

Examples:

• /shopify-apps/judgeme-review/
• /shopify-apps/judgeme-vs-loox/
• /shopify-apps/best-review-apps/

The final URL structure should follow Blinto’s approved website architecture.

27. Content Brief Quality Assurance Checklist

Before submitting the brief, confirm:

• The correct topic and content format are used.
• The target audience is specific.
• The merchant problem is clear.
• Search intent is correctly defined.
• The primary keyword matches the intent.
• Secondary keywords are relevant.
• Search results were analyzed.
• Relevant competitors were reviewed.
• Content gaps are useful, not superficial.
• The content angle is differentiated.
• Important entities are included.
• User questions are relevant.
• The outline is logically structured.
• Every section has a clear purpose.
• Evidence is mapped to the correct sections.
• Technical claims are marked for careful wording.
• Internal links are planned.
• The CTA matches the reader’s need.
• Visual requirements are practical.
• Testing limitations are disclosed.
• Pricing verification date is included.
• The writer has enough information to begin.
• The brief avoids unnecessary repetition.
• The brief supports the selected content cluster.
• The article can provide better value than current competitors.

28. Approval Process

The completed brief should be reviewed by the Content Lead or SEO Lead.

Reviewer Responsibilities

The reviewer must confirm:

• The brief matches the approved project topic.
• The research has been used correctly.
• Search intent is satisfied.
• The outline is complete.
• The content angle is strong.
• The article will provide original value.
• Keywords are mapped naturally.
• The evidence plan is clear.
• The writer instructions are understandable.
• Internal links and CTAs are appropriate.
• Trust and disclosure requirements are included.
• The brief does not encourage unsupported claims.

Approval Decisions

Approval must be recorded in ClickUp.

29. ClickUp Requirements

Status Changes

At the beginning:

Research Completed → Brief Creation

After the first brief draft:

Brief Creation → Brief Review

After approval:

Brief Review → Brief Approved

SOP 3 ends when the task reaches Brief Approved.

Required ClickUp Fields

• Final working title
• Content type
• Primary keyword
• Search intent
• Target audience
• Content strategist
• SEO reviewer
• Brief due date
• Brief approval date
• Recommended word range
• Content cluster
• Relevant service page
• Testing level
• Research document link
• Evidence-folder link
• Content-brief link
• Approval status

Required Attachments

• Final content brief
• Keyword research
• Competitor analysis
• Content-gap analysis
• Entity and semantic map
• User-question research
• Internal-linking plan
• Evidence map
• Visual requirements
• Approval notes

30. Recommended Timeline

Single App Review Brief

Estimated total: 6–10 working hours

Comparison Article Brief

Estimated total: 8–12 working hours

Additional time may be required to map equivalent features, pricing tiers, and decision criteria.

Category Review Brief

Estimated total: 10–16 working hours

Additional time may be required because several apps, use cases, and keywords must be mapped consistently.

31. Common Mistakes to Avoid

Do not:

• Start the brief before app research is approved.
• Choose the primary keyword only by search volume.
• Copy a competitor’s outline.
• Create headings only to insert keywords.
• Ignore the merchant’s actual decision.
• Turn every feature into a separate section.
• Include entities that do not improve the content.
• Create a long FAQ with repetitive questions.
• Use unverified app claims.
• Ignore hands-on research findings.
• Hide negative findings.
• Recommend an app without defining who it suits.
• Use the same content angle for every app.
• Force a universal winner in comparison content.
• Add irrelevant internal links.
• Use an aggressive service CTA.
• Include exact pricing without a verification date.
• Claim full testing when testing was partial.
• Submit a brief without evidence mapping.
• Give the writer vague instructions such as “write helpful content.”
• Move the task to writing before approval.

32. Escalation Rules

Escalate to the Project Lead when:

• Search intent differs significantly from the approved topic.
• The primary keyword does not support the planned content format.
• Research findings contradict the planned recommendation.
• Competing content is significantly stronger than expected.
• The article cannot provide a meaningful unique value.
• The app changed pricing or features during brief creation.
• Important evidence is missing.
• Technical claims remain unresolved.
• The content may create legal or reputational risk.
• A founder requests control over the outline or verdict.
• The content overlaps with an existing Blinto page.
• Two teams disagree about the search intent or content angle.
• The planned CTA conflicts with editorial independence.

The Project Lead may approve a new angle, return the task to research, change the format, combine topics, delay publication, or cancel the content.

33. Definition of Done

SOP 3 is complete only when:

• The approved research has been reviewed.
• The content format is confirmed.
• The target audience is defined.
• The merchant problem is documented.
• Search intent is clear.
• The primary and secondary keywords are selected.
• Search results and competitors have been analyzed.
• Meaningful content gaps have been identified.
• The content angle is approved.
• The unique value proposition is clear.
• Primary and secondary entities are mapped.
• User questions are prioritized.
• Evidence is mapped to the outline.
• The complete H1, H2, and H3 structure is ready.
• Section-level writer instructions are included.
• Internal links are planned.
• CTA requirements are defined.
• Visual requirements are documented.
• Trust and disclosure requirements are included.
• Metadata recommendations are prepared.
• The content brief passes QA.
• The brief has been approved.
• ClickUp contains all required fields and attachments.
• The ClickUp task status is Brief Approved.

If any required item is missing, the task is not ready for SOP 4.

34. Handoff to SOP 4

After approval, the SEO Strategist or Content Strategist prepares a concise handoff for the assigned writer.

Required Writer Handoff

• Final working title
• Content type
• Primary keyword
• Target audience
• Merchant problem
• Search intent
• Main content angle
• Testing level
• Quick verdict direction
• Best-fit merchant
• Poor-fit merchant
• Key findings
• Important limitations
• Required sections
• Required evidence
• Required tables
• Required visuals
• Internal links
• CTA direction
• Claims to avoid
• Required disclosures
• Word-count guidance
• Due date
• Reviewer

The task then moves to:

SOP 4: Shopify App Review Content Writing

SOP 4 will define:

• How the writer should use the approved brief
• How to write category, single-app, and comparison content
• How to present testing evidence
• How to explain features and merchant value
• How to write pros, cons, verdicts, and comparisons
• How to avoid unsupported claims
• How to maintain editorial independence
• How to format the first draft
• How to complete the writer’s self-review
• How to submit the draft for editorial review