Skip to main content
Prompts B2B Manufacturing Homepage Tech-SEO Diagnostic

analyst analysis template risk: low

B2B Manufacturing Homepage Tech-SEO Diagnostic

Performs a quick diagnostic on provided homepage HTML source code for a B2B manufacturing client targeting overseas markets, identifying tech stack components, one outdated element…

PROMPT 

${instruction}
Based on the homepage HTML source code I provide, perform a quick diagnostic for a B2B manufacturing client targeting overseas markets. Output must be under 200 words.

1️⃣ Tech Stack Snapshot:
- Identify backend language (e.g., PHP, ASP), frontend libraries (e.g., jQuery version), CMS/framework clues, and analytics tools (e.g., GA, Okki).
- Flag 1 clearly outdated or risky component (e.g., jQuery 1.x, deprecated UA tracking).

2️⃣ SEO Critical Issues:
- Highlight max 3 high-impact problems visible in the source (e.g., missing viewport, empty meta description, content hidden in HTML comments, non-responsive layout).
- For each, briefly state the business impact on overseas organic traffic or conversions.

✅ Output Format:
• 1 sentence acknowledging a strength (if any)
• 3 bullet points: ${issue} → [Impact on global SEO/UX]
• 1 low-pressure closing line (e.g., "Happy to share a full audit if helpful.")

Tone: Professional, constructive, no sales pressure. Assume the client is a Chinese manufacturer expanding globally.

INPUTS

instruction REQUIRED

Instruction including the homepage HTML source code to analyze

REQUIRED CONTEXT

  • homepage HTML source code

ROLES & RULES

  1. Keep output under 200 words.
  2. Identify backend language, frontend libraries, CMS/framework clues, and analytics tools.
  3. Flag 1 clearly outdated or risky component.
  4. Highlight max 3 high-impact SEO problems visible in the source.
  5. For each issue, briefly state the business impact on overseas organic traffic or conversions.
  6. Use exact output format: strength sentence, 3 bullet points, closing line.
  7. Maintain professional, constructive tone with no sales pressure.
  8. Assume client is a Chinese manufacturer expanding globally.

EXPECTED OUTPUT

Format
bullet_list
Schema
bullet_list · Strength acknowledgment sentence, 3 bullet points: issue → impact, Closing line
Constraints
  • under 200 words
  • 1 sentence acknowledging a strength
  • max 3 bullet points: issue → impact on global SEO/UX
  • 1 low-pressure closing line
  • professional constructive tone, no sales pressure

SUCCESS CRITERIA

  • Provide tech stack snapshot including one risky component.
  • Highlight up to 3 SEO critical issues with business impacts.
  • Acknowledge a strength if present.
  • End with low-pressure closing.
  • Stay under 200 words.

FAILURE MODES

  • Exceeding 200 word limit.
  • Highlighting more than 3 issues.
  • Using salesy or unprofessional tone.
  • Omitting business impacts on overseas markets.
  • Failing to flag a risky component.
  • Not basing analysis on provided HTML source.

CAVEATS

Dependencies
  • Homepage HTML source code
Missing context
  • Specific homepage HTML source code (to be inserted via ${instruction}).
Ambiguities
  • Output format uses '${issue}' which is unclear if literal text or a placeholder.
  • Does not explicitly handle cases with zero outdated components or zero SEO issues (though 'max 3' and 'if any' for strength imply flexibility).

QUALITY

OVERALL
0.91
CLARITY
0.88
SPECIFICITY
0.92
REUSABILITY
0.95
COMPLETENESS
0.87

IMPROVEMENT SUGGESTIONS

  • Replace '${issue}' in output format with a clear placeholder like '[Issue]' and document it.
  • Add brief guidance: 'If no outdated component, note "None detected" in Tech Stack section.'
  • Explicitly state: 'Keep total output under 200 words; aim for concise bullets.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR ANALYST