landing-page-conversion-audit
Audit Landing Pages for Conversion Friction
Competing actions and complex forms can reduce landing page conversions. This guide helps your AI review HTML and CSS and prioritize technical improvements.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "landing-page-conversion-audit" from https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit.md and its manifest at https://skillstore.io/api/skills/nexaiguy-landing-page-conversion-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「landing-page-conversion-audit」を使用しています。 Review supplied hero markup containing a signup button and three social links for a signup-focused campaign.
期待される結果:
- Finding: Three social links introduce competing destinations beside the primary signup action.
- Priority: High for a signup-focused campaign; the conversion impact remains unmeasured.
- Recommendation: Move social links below the hero and retain a prominent primary CTA.
- Validation: Inspect desktop and mobile layouts, then test the revised page against the current version.
「landing-page-conversion-audit」を使用しています。 Audit a signup form containing 12 required fields, including information not needed to create an account.
期待される結果:
- Finding: Twelve required fields create potential signup friction.
- Priority: High; confirm which fields are necessary before removing them.
- Recommendation: Keep essential account fields and collect optional profile details after signup.
- Validation: Check validation rules and compare completion rates after an approved experiment.
セキュリティ監査
安全All three static findings are false positives: the URLs provide attribution, and the footer contains no system reconnaissance instructions. No evidence found of prompt injection, credential access, or data exfiltration in the supplied guide. The package contains instructions only; advertised scripts and templates are absent.
リスク要因
🌐 ネットワークアクセス (2)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-landing-page-conversion-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-landing-page-conversion-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
nexaiguy. (2026). landing-page-conversion-audit security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-landing-page-conversion-audit-2026,
author = {nexaiguy},
title = {landing-page-conversion-audit security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit/audits/1},
note = {Author version 1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "landing-page-conversion-audit security audit report (audit version 1)"
version: "1.2"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-landing-page-conversion-audit/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-landing-page-conversion-audit:audit:1"
description: "Skillstore immutable audit report identifier"
バリアントを比較
インストール可能なバリアント 2 件各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。
このバリアントが首位の理由
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review Campaign Readiness
Identify competing hero actions, long forms, and missing trust elements before directing paid traffic to a landing page.
Prioritize Frontend Fixes
Review landing page HTML and CSS for structural friction and turn findings into a severity-ranked implementation list.
Prepare Client Audit Reports
Create a consistent technical review of client landing pages while separating observed issues from assumptions requiring browser verification.
これらのプロンプトを試す
Review this landing page HTML for conversion friction: [HTML]. Rank observed issues by severity and suggest a technical fix for each.
Audit the supplied hero HTML and CSS: [content]. Check primary CTA prominence, competing actions, outbound links, and headline visibility. State any uncertainty.
Review [HTML and CSS] for form friction, contact barriers, tap-target issues, and overflow risks. Cite structural evidence and identify checks requiring browser verification.
Audit [HTML and CSS] for a campaign targeting [audience] with [primary action]. Group findings by conversion family and severity. Include evidence, fixes, and validation steps. Separate observed issues from hypotheses; do not claim measured uplift.
ベストプラクティス
- Provide the relevant HTML and CSS, target audience, campaign goal, and primary conversion action.
- Require evidence for every finding and distinguish structural observations from visual assumptions or measured results.
- Verify recommendations in desktop and mobile browsers, then measure conversion changes through controlled testing.
回避
- Expecting the public guide to run an automated scanner or install scripts absent from the package.
- Treating severity labels as proof of conversion losses, guaranteed revenue gains, or legal noncompliance.
- Submitting only a URL when the host agent cannot retrieve pages, or expecting static markup to reveal client-rendered content.