AI Effects Page Copywriter

AI Effects Page Copywriter

Use this skill to research and create English SEO copy for AIReel-style AI Effects pages. The page's job is simple: match a concrete search need, show the effect fast, explain the input-to-output transformation, reduce friction, and move the user into generation.

For pages under aireel.net/ai-effects/, the AIReel fixed page blueprint below takes precedence over generic landing-page conventions. In particular, do not replace the video sample showcase with text-only examples, do not write more than four feature cards, and always return the complete TDK package.

This is a two-stage deliverable, not a copy-only shortcut:

1. Build a keyword research brief and map one search-intent cluster to the page.
2. Write the page around that cluster, insert keywords naturally, and run a coverage and cannibalization review.

If the user asks for keyword research only, stop after Stage 1. If the user asks for copy only, still perform Stage 1 whenever usable evidence is available. If no live search or keyword dataset is available, use an evidence-light brief based on the supplied terms and visible competitor/SERP language, label the limitation, and do not invent search volume, difficulty, CPC, traffic, or ranking claims.

End-to-End Workflow

Follow these stages in order. Do not jump directly to title formulas before deciding which query cluster the page serves.

Stage 0: Define the page and its evidence

Collect the page inputs below. Separate facts supplied by the user or product documentation from assumptions. Record the research date and sources.

• Page/effect name and proposed slug.
• Product, page, or competitor URLs to inspect.
• Output format: image, video, image and video, portrait, clip, template, reading, or style preview.
• Input format: photo, selfie, two photos, text, script, reference image, audio, or video.
• Audience, use cases, location, and language variant (en-US, en-GB, or global English).
• Product facts: pricing/free credits, sign-up, processing time, privacy, resolution, templates, download, sharing, and commercial-use terms.
• Existing URL inventory or sitemap, when available, for internal links and cannibalization checks.

Ask for missing information only when it changes the target query or creates a material compliance/claim risk. Otherwise use a conservative assumption and mark it.

Stage 1: Research and expand the keyword set

Start with 1-3 seed concepts from the effect, user problem, input, and desired output. Expand each seed across the following modifier groups. Keep only phrases that describe a real use case the product can satisfy.

• Core object/effect: ai dance, photo to anime, headshot, background remover.
• Tool intent: generator, maker, creator, filter, changer, app, online.
• Input/output: from photo, from image, photo to video, text to video, video generator.
• Use case/audience: for TikTok, for profile picture, for LinkedIn, for couples, for product photos.
• Attributes: free, without editing, in seconds, template, realistic, cinematic only when supportable.
• Questions and objections: how to, what is, is it free, what photo works best, can I download.

Required live SERP pass

When live search is available, do not research only the exact-match seed. Build a focused query set from the product's real input, output, object, and use case. Normally inspect 6-10 queries, including:

• The exact primary seed.
• One input variant, such as [effect] from photo or upload photo to [effect].
• One output variant, such as [effect] video generator, [effect] avatar, or [effect] portrait.
• One tool synonym, such as maker, creator, changer, or try on.
• One high-intent attribute surfaced by the SERP, such as free, online, or no sign up; retain it only if the product supports the claim.
• One object, style, audience, or use-case variant discovered in result titles, snippets, People Also Ask, related searches, or autocomplete.

For each query, inspect the first 5-10 relevant organic results when available. Record result titles, snippets, recurring modifiers, PAA questions, related searches, and concrete page concepts. A modifier that appears repeatedly across independent results or in Google's related-search surfaces is stronger evidence than a phrase invented from a formula. Stop when new queries no longer reveal a distinct intent or vocabulary set.

Create a compact SERP Language Evidence table:

Do not copy competitor sentences. Translate the observed intent into original, product-specific content.

Use sources in this order when they are available:

1. First-party performance data: Google Search Console queries, analytics landing pages, and the site's sitemap/URL inventory.
2. Reliable keyword datasets: Google Keyword Planner, Ahrefs, Semrush, Moz, or an equivalent export supplied by the user.
3. Live SERP evidence: result titles, snippets, People Also Ask, related searches, autocomplete, and recurring page sections.
4. Competitor evidence: indexable titles, H1s, H2s, FAQs, and landing-page language from relevant pages.

Use web research or an available browser for live sources. Cite the URL/source and date in the brief. Never present a competitor's wording as original copy; use it only to understand intent and expectations.

For every candidate keyword, capture the following fields. Use unknown rather than guessing a metric.

Classify intent as one primary label: transactional, commercial investigation, informational, navigational, or inspirational. Also record the immediate job-to-be-done, such as “generate a dance video from one photo.” A keyword is not useful merely because it contains AI and the effect name; it must match the product's actual input, output, and user expectation.

Stage 1B: Cluster, score, and choose targets

Cluster keywords by shared intent and likely SERP overlap, not by spelling alone. Treat close variants as one cluster when a searcher would expect the same page. Create a separate page only when the SERP, input/output, audience, or task is materially different.

Score candidates transparently on a 0-5 scale:

• Relevance: can this product directly satisfy the query?
• Intent strength: how close is the searcher to trying or choosing a tool?
• Business value: does the query support the page's activation or conversion goal?
• SERP fit: do comparable results match this page type and output?
• Evidence confidence: how strong and current is the source data?
• Cannibalization risk: would this compete with an existing URL?

Use this directional priority score when numeric data is incomplete:

priority = 3*relevance + 2*intent + 2*business value + SERP fit + confidence - 2*cannibalization risk

Do not treat the score as a forecast of traffic or ranking. Use measured volume/difficulty when available, and explain any judgment-based scores.

Select:

• One primary keyword: the clearest, highest-priority phrase for this URL.
• 6-12 secondary and long-tail keywords when the SERP supports them: close variants plus input, output, style/object, and use-case sub-intents that the page can genuinely answer.
• 4-8 question keywords: FAQ or explanatory opportunities.
• 10-25 related entities and semantic terms: concrete inputs, outputs, actions, styles, subjects, settings, use cases, and objections that make the topic specific without repeating the exact phrase.
• Exclusions: irrelevant, unsupported, unsafe, misleading, or cannibalizing terms, with a short reason.

The selected set must cover more than spelling variants. Include at least one term from each applicable category: input, output, subject/style, use case, and question/objection. When a category is unsupported by the product, exclude it explicitly instead of forcing it into the copy.

Do not select multiple primary keywords simply to look comprehensive. If two terms have different SERPs or require different product flows, recommend separate pages or a hub-and-spoke plan.

Stage 1C: Check site architecture and cannibalization

Compare the chosen cluster with existing page titles, H1s, slugs, and known target keywords. Flag:

• Two URLs targeting the same primary intent.
• A broad hub page competing with a specific effect page.
• A variant that should be an H2/FAQ rather than a new URL.
• An internal link whose anchor text implies a different destination intent.

Recommend one action for each conflict: keep, merge, redirect, differentiate the intent, or create a new page. Do not silently assign the same exact primary keyword to several pages.

Stage 2: Produce the keyword-to-page map

Before drafting prose, map each selected term to one job and one page location. The map prevents both keyword stuffing and accidental omission.

Map one primary keyword to the title, H1, and opening copy. Assign secondary terms to distinct sections where they genuinely help the reader. Put question terms in FAQs only when the answer is useful. Use semantic terms as natural language, not as a checklist. Map related effects to relevant internal-link destinations and use descriptive anchors.

Stage 2B: Build a content-specificity matrix

Before drafting, turn keyword evidence into concrete content. Fill at least three applicable rows in each category below; use not supported when product evidence rules a category out.

Specificity must be traceable: every chosen example should come from product evidence, visible assets, live SERP language, or a reasonable category convention marked as editorial direction. Do not list options the product cannot produce. For rights-sensitive topics, use original archetypes and generic visual traits rather than protected character names, logos, signature costumes, or scenes.

Stage 3: Write and insert the copy

Draft the page only after the brief and map are complete. Follow the page structure below, but let the chosen intent determine section wording. Every keyword insertion must clarify the user's task, input, output, or next action.

Keyword Placement Rules

Use the primary keyword naturally in:

• SEO title: once, near the front when readable.
• H1: once, in a clean user-facing form.
• Meta description: once when it fits naturally; prioritize a clear input-to-output promise.
• Hero opening sentence or first 100 words: once or a close grammatical variant.
• One relevant H2 or body section only when it reads naturally.

Use secondary keywords in the section mapped to their intent. Use question keywords as actual FAQ questions or as subtopics in explanatory copy. Use semantic terms across examples, steps, benefits, captions, image alt text, and internal links only where the underlying asset or destination supports them.

Do not force an exact-match phrase into every heading, paragraph, image alt, or CTA. Do not set an arbitrary keyword-density target. A page passes when the primary intent is unmistakable, the mapped questions are answered, and the language sounds like native English. Delete a keyword when it makes a sentence awkward, redundant, or less accurate.

When a target phrase has several grammatical forms, prefer the form a native searcher would understand. Do not use awkward constructions such as AI Dance Generator generator or repeat free in every module. Claims such as free, fast, private, in seconds, no sign-up, commercial use, and most realistic require product evidence.

Brand mention budget

The effect and user's result should lead the page; the brand should identify the tool, not become a repeated keyword. For a normal AIReel effect page:

• Use AIReel no more than 2-3 times in visible effect-page copy, excluding navigation or the site's shared footer component.
• A brand mention is optional in the Meta Title. Prefer the query and specific result when the title is already long.
• Use the brand once in the Hero or first workflow mention, then use the generator, the effect, or direct verbs where the reference is clear.
• Do not repeat the brand in every step, feature card, FAQ answer, CTA, or related-link item.
• Count exact visible mentions during validation. Research notes, URLs, implementation notes, and citations do not count toward the visible-copy budget.

Stage 4: Validate the finished page

Run this review after drafting. Report failures instead of quietly patching over evidence gaps.

• Coverage: the primary keyword appears in the title, H1, and opening copy; every selected secondary and question keyword has a mapped status.
• Long-tail breadth: the selected terms cover applicable input, output, subject/style, use-case, and objection categories, and each used term appears in a relevant module rather than only in Meta Keywords.
• Specificity: the page includes concrete, keyword-relevant subjects, scenes, outputs, and uses supported by the content-specificity matrix.
• Intent: the first viewport answers what the effect does, what the user uploads, and what the output is.
• Naturalness: remove awkward exact matches, repeated modifiers, and headings written for robots rather than readers.
• Brand restraint: visible brand mentions stay within the budget and do not replace useful product language.
• SERP fit: title, snippet, headings, format, and depth reflect the observed intent without copying competitors.
• Architecture: the page has one primary target and does not duplicate an existing page's job.
• Claims: every product promise is verified, qualified, or marked [verify].
• Accessibility and assets: captions and alt text describe real visible content; do not use a keyword as alt text when it does not describe the image.
• Safety: sensitive effects include the required consent, privacy, age, or entertainment framing.

Return a short SEO Validation table with check, result, evidence, and next action. If a metric was unavailable, say so explicitly rather than assigning a pass based on guesswork.

Research Basis

This skill is distilled from high-surface AIReel English /ai-effects/ pages reviewed on 2026-08-28, including AI Background, AI Kiss, AI Dance, AI Headshot, AI Action Figure, AI Age, AI Hug, AI Photo to Anime, AI Head Swap, AI Baby, AI Bullet Time, AI Earth Zoom, AI Movie, AI Hairstyle, AI Hanfu, AI Palm Reading, AI Fisheye, AI Jiggle, AI Twerk, and AI Breast Expansion pages.

The strongest repeating pattern is a fixed page module sequence:

1. TDK package: Meta Title, Meta Description, Meta Keywords, plus the canonical URL/proposed slug recorded as implementation metadata.
2. Generator hero: H1, introduction, effect/preset area, and generation CTA.
3. Video sample showcase: a visual sample block immediately after the hero. On the live AI Baby page this is a three-video block; other effects may use a different number of assets, so verify the page rather than inventing a count.
4. Three-step how-to section.
5. One benefits section with exactly four feature cards and a CTA.
6. FAQ section, normally six questions.
7. More AI Effects links.
8. AIReel's global all-in-one video CTA in the footer.

Input Checklist

Before writing, identify or ask for:

• Effect name: the exact public name, such as AI Dance Video Generator.
• Primary keyword: usually AI [Effect] Generator, AI [Effect] Video Generator, [Effect] AI, or [Effect] Changer.
• Slug: usually lowercase and hyphenated, such as ai-dance or ai-photo-to-anime.
• Output type: image, video, image and video, portrait, clip, template, reading, or style preview.
• Input type: photo, selfie, two photos, text, script, image, reference image, audio, or video.
• Main use cases: social posts, portraits, ads, entertainment, professional profile, product visuals, cinematic clip, meme/trend, personal preview.
• Real product claims: free credits, no sign-up, privacy, processing speed, resolution, commercial use, templates, examples. Do not invent unsupported claims.
• Safety constraints: identity, minors, intimate themes, body changes, medical/fortune-like claims, copyrighted characters, or public figures.

If details are missing, make conservative assumptions and leave bracketed placeholders only for claims that must be verified.

Page Archetypes

Classify the page before writing:

• Transformation page: changes identity, style, age, body, clothes, background, hairstyle, or anime/live-action style.
• Motion/trend page: turns a still image into a viral dance, hug, kiss, twerk, jiggle, bullet-time, or Earth zoom video.
• Utility page: headshots, product backgrounds, ads, storyboard, interior design, or professional visuals.
• Cinematic page: movie, horror, vampire, mermaid, heaven, bullet time, Earth zoom, fisheye, or action scenes.
• Relationship/emotion page: hug, kiss, baby, younger self, loved ones, couples, or memory scenes.
• Sensitive page: body, intimate, age, baby/child, face/head swap, palm reading, public figure, or adult-coded effects.

The archetype controls tone. Utility pages should feel efficient and credible. Trend pages can be playful and social. Sensitive pages need clearer consent, privacy, and realistic-limit language.

SEO Title Formula

Write 3 title options, then choose the most natural one. Keep the final title around 50-60 characters when possible.

Useful formulas:

• Free AI [Effect] Generator Online
• AI [Effect] Video Generator from Photo
• Free AI [Effect] Generator - Turn Photos into [Result]
• AI [Effect] Changer | See [Result] on Your Photo
• [Effect] AI | Create [Result] Online
• AI [Effect] Generator for [Audience or Use Case]

Title rules:

• Put the primary keyword near the front.
• Use Free only if the product has a real free path or free credits.
• Use Online when the web workflow matters.
• Use Video or Photo when it clarifies the output.
• Avoid vague titles like Amazing AI Effects.
• Avoid unsupported superlatives like best, perfect, or most realistic unless evidence is provided.

Meta Description Formula

Write one 130-155 character meta description. It should say what the user inputs, what the AI creates, and why the workflow is easy.

Formula:

[Create/Turn/Upload] [input] into [specific result] with [effect name]. [Add one friction reducer: online/free/fast/no editing/templates/download/share].

Good description ingredients:

• Input: photo, two photos, selfie, text, script, image, reference image.
• Output: AI video, portrait, style preview, background, cinematic clip, social-ready clip.
• Use case: TikTok, Reels, LinkedIn, product photos, memes, ads, profile photos, story scenes.
• Friction reducer: free trial, online, in seconds, no editing skills, templates, private upload.

AIReel Page Template

Use this exact order for English pages under /ai-effects/. The copy supports the existing UI and should not invent visual modules that the page does not contain.

0. Complete TDK Package

Return all three fields before the body copy:

• Meta Title: one query-led title, usually around 50-60 characters.
• Meta Description: one input-to-output description, usually around 130-155 characters.
• Meta Keywords: a comma-separated list of relevant primary, secondary, and long-tail terms for the CMS. Keep it focused; do not repeat the same phrase or treat this field as a ranking guarantee.

Also record the canonical URL or proposed slug when the user provides it. Meta Keywords are included for TDK/CMS completeness even though major search engines generally do not use them as a primary ranking signal.

1. Generator Hero

This is the first visible content module. Write:

• H1: a clear effect name plus the output, such as [AI Effect] Generator or [AI Effect] Photos & Videos Generator.
• One short introduction: explain the input, transformation, and output.
• Preset/effect labels only when the product supplies them. Do not invent preset names.
• Generator CTA labels such as Upload, Generate Now, or the page-specific action when verified.

Keep the hero direct. The first sentence should tell the user what they can make and what they need to upload.

2. Video Sample Showcase

This is the second content module after the hero. Treat it as a visual sample section, not a text-only proof section.

• H2: outcome-led title, such as Future Baby Preview or Create Viral AI Dance Videos from Any Image.
• One short supporting paragraph explaining what the samples demonstrate.
• Sample inventory: as a non-visible implementation note, identify the available video samples, their role, and their visible result. Do not fabricate sample names, durations, formats, or output claims.
• Optional CTA: one button that leads back to the generator.

The visible copy for this module is normally the H2 and supporting paragraph; write individual video titles or captions only when the UI contains them. Include an asset inventory separately for editorial/implementation use. Do not substitute 3-6 generic example bullets for the video showcase. If video assets cannot be inspected, mark the inventory [video asset to verify].

3. How-To in Three Steps

Use the page's existing three-step flow:

1. Access AIReel or open the effect.
2. Upload/select the supported input or preset.
3. Generate the result and keep/explore/share it.

Use the actual product flow when it differs. Write one H2, Step 1, Step 2, Step 3, a short paragraph for each, and one CTA below the steps. Do not add a fourth step just to place another keyword.

4. Feature Section with Exactly Four Cards

Use one H2, usually in the pattern Everything You Need for AI [Effect], followed by exactly four feature cards. This is the module represented in the user's reference screenshot.

Each card contains:

• One H3 benefit title.
• One concise description connecting a verified product capability to a user outcome.
• An icon/image label only when the asset exists or is supplied.

Design the four cards from the target keyword's actual search intents and content-specificity matrix. Give each card a different job, normally chosen from: input transformation, target-specific subjects/styles, target-specific scenes/outputs, and target-specific use cases or objections. The card set must make sense only for this effect; if the same four titles could be pasted onto an unrelated generator page, rewrite them.

Avoid default card sets such as Easy to Use, Fast Results, Photo & Video, and More Effects. Ease or speed may appear inside a card only when it supports a more specific benefit. Do not produce five or six cards, a separate prompt-ideas section, or a second benefits grid for this template. Put one page CTA below the four cards.

5. FAQ

Use one H2, usually Frequently Asked Questions, followed by the page's six most useful questions. Match the live page's question pattern: capability, input quality, output type, time/credits, failure/limitations, and privacy or usage rights. Each answer should be concise and product-grounded. Do not add FAQ questions just to repeat keywords.

6. More AI Effects

Use the existing More AI Effects module. Recommend 6-12 relevant links only when their URLs or names are known. Group by adjacent user intent where useful and use descriptive anchors. Do not repeat the current page as an internal link to itself.

7. Global Footer CTA

AIReel pages end with the site's global all-in-one video-generation CTA, currently expressed as Create Stunning AI Videos All in One Stop. Treat this as a shared footer module, not a new effect-specific content section. Keep the page-specific CTA above it and do not duplicate the entire footer copy in the effect content brief.

Modules That Are Not Default

Do not add these as standalone modules to the AIReel template unless the user explicitly requests them or the live page contains them:

• A generic proof/examples list in place of the video sample showcase.
• A standalone prompt-ideas section.
• More than four feature cards.
• A second final CTA section that duplicates the global footer CTA.
• Long educational essays or technical model explanations.

Tone and Style

Write in clear, natural English for search users who want to try the effect quickly.

Use:

• Active verbs: turn, create, upload, choose, generate, preview, download, share.
• Concrete nouns: photo, selfie, portrait, clip, template, background, camera move, style.
• Short paragraphs: 1-3 sentences.
• Benefit-led headings: headings should tell users what they get.
• Realistic modifiers: smooth, natural, cinematic, social-ready, professional, playful, fast, simple.

Avoid:

• Generic AI filler: unleash your creativity, revolutionize, next-level, magical.
• Dense technical model explanations unless the user asks.
• Keyword stuffing.
• Unsupported certainty: guaranteed, perfect, flawless, best.
• Claims about privacy, speed, resolution, commercial use, or free unlimited access unless verified.

Natural English / Anti-Template Pass

Run a dedicated naturalness pass after the SEO pass. Search optimization should make the page easier to find, not make every sentence sound alike.

• Lead with the user's visible result and the required input. Do not open every section with Turn, Transform, or Explore.
• Vary sentence length and rhythm. Use one clear idea per sentence instead of stacking three abstract benefits and several adjectives.
• Prefer plain, specific verbs such as upload, pick, watch, try, keep, and share over inflated phrases such as bring your vision to life or unlock limitless creativity.
• Use concrete details that belong to the effect, such as a suit, skyline, portrait, or short clip. Remove generic words such as powerful, dynamic, immersive, next-level, and seamless when they do not add information.
• Keep headings conversational and outcome-led. A heading should sound like something a product team would actually put on the page, not a keyword assembled from a formula.
• Write CTAs as the next useful action (Create Your Superhero, Try the Effect) rather than an abstract promise.
• Keep [verify], [to verify], and implementation notes outside visible page copy. Put them in Product and Safety Constraints, SEO Validation, or clearly labeled non-visible asset notes.
• Read the copy aloud once. Delete repeated framing, unnecessary introductory phrases, and any sentence that would sound unnatural in a product demo.

Sensitive Content Handling

Some AI effect pages involve bodies, intimacy, age, babies, face/head swapping, or relationship scenes. Keep these pages safe, consent-forward, and non-graphic.

Rules:

• Do not sexualize minors or age transformation results.
• Do not imply users can create non-consensual intimate content.
• For kiss, hug, body, swap, or adult-coded pages, include consent and private-upload reminders.
• For palm reading or similar pages, frame outputs as entertainment or visual interpretation, not factual prediction.
• For head swap, public figures, idols, or celebrity-like use cases, avoid deception and impersonation claims.
• For professional/ads/product pages, avoid commercial-rights claims unless the product terms support them.

Output Template

When asked to research and write a full page, read references/seo-package-template.md and produce its six sections in this presentation order:

1. Page Copy: complete TDK, Hero, video sample showcase, three-step How-To, exactly four feature cards, six-question FAQ, More AI Effects, and the shared footer CTA.
2. Research Scope and Evidence.
3. Keyword Research Brief.
4. Keyword-to-Page Map.
5. Product and Safety Constraints.
6. SEO Validation.

Perform research and fact-checking before drafting internally, but put the usable page result first in the user-facing document. Keep the research and reasoning concise after the copy. When asked for research only, return the research sections without inventing page copy. Do not omit the keyword map or SEO validation table because the user asks for copy only.

Quality Checklist

Before finalizing, verify:

• A source-backed or evidence-light keyword brief exists before the copy.
• Exactly one primary keyword is selected for this URL.
• Search volume, difficulty, CPC, trend, and ranking claims are cited or marked unknown.
• Keywords are clustered by search intent/SERP overlap and checked against existing URLs.
• The keyword-to-page map assigns each selected term a location and final status.
• A live SERP pass used 6-10 focused queries when browser evidence was available, and the brief includes a SERP Language Evidence table.
• Secondary terms cover applicable input, output, subject/style, use-case, and objection categories rather than only close spellings of the primary keyword.
• A content-specificity matrix supplies concrete subjects, scenes, outputs, uses, and objections before prose is drafted.
• The meta title includes the primary keyword near the front and stays concise.
• The meta description names input, output, and ease without becoming a keyword list.
• The H1 is readable and not overloaded.
• The hero explains the transformation within the first sentence.
• The complete TDK package is present: Meta Title, Meta Description, Meta Keywords, and Canonical URL/proposed slug.
• The page follows the AIReel order: TDK → hero → video sample showcase → 3 steps → exactly 4 feature cards → FAQ → More AI Effects → shared footer CTA.
• The second content module is a video/visual sample showcase, with an asset inventory tied to real videos or [video asset to verify]; a text-only examples list does not pass.
• The feature section contains exactly four cards and no standalone Prompt Ideas section unless the live page explicitly contains one.
• Each feature card carries a distinct keyword-relevant intent; the four-card set could not be reused unchanged for an unrelated effect.
• The FAQ contains six useful questions by default, covering capability, input, output, access/credits or time, limitations, and privacy/consent/usage rights as applicable.
• The shared footer CTA is not duplicated as a second effect-specific final CTA.
• Each H2 maps to one user intent, and no heading contains an awkward exact match.
• FAQs answer researched objections and question keywords, not generic marketing prompts.
• Primary, secondary, and semantic terms read naturally; there is no density target or stuffing.
• Selected long-tail terms appear in useful modules, not only in Meta Keywords or the research appendix.
• Visible AIReel mentions stay within the 2-3 mention budget, excluding navigation and the shared footer component.
• The copy avoids unsupported product claims and leaves verification flags visible.
• Sensitive effects include consent, privacy, age, or entertainment framing where needed.
• Video captions, alt text, anchors, and examples describe the actual asset or destination.
• The English sounds native, direct, and useful.

Mini Example

Input:

• Effect: AI Mermaid
• Primary keyword: AI Mermaid Generator
• Input: selfie or portrait
• Output: mermaid portrait or short fantasy video

Output excerpt:

## Meta Title
Free AI Mermaid Generator from Photo Online

## Meta Description
Turn a selfie or portrait into a fantasy mermaid image or video with AI. Upload a photo, choose an ocean-inspired style, and create online in minutes.

## H1
AI Mermaid Generator from Photo

## Hero
Turn your portrait into an ocean-inspired mermaid scene with AI. Upload a selfie, choose a fantasy style, and create a graceful mermaid image or short video for avatars, stories, and social posts without manual editing.

CTA: Create Your Mermaid Look