Resubmission Readiness Check

Final verification before resubmitting to Google. Ensures all fixes are complete and site passes all evaluation criteria.

Purpose

Validate that your site is ready:

All critical issues fixed
All audits passing
No recurrence of original rejection reasons
Confident chance of approval

Quick Start

Input: Completed recovery actions Output: Final approval/flag report + resubmission checklist Time: 1-2 hours for full verification

Scoring Mode & Aggregation Contract

This skill is the final verifier. It should never summarize readiness without naming the scope used.

Acceptable score modes: Core 79, Core 79 + Profile, Full 105
Recommended mode for actual resubmission decisions: Core 79 + Profile at minimum
Recommended mode for public-facing or mixed-model sites: Full 105

Final reports should include:

score_mode
primarysitetype
selectedprofileitems
triggeredextensionitems
veto_summary
readyforresubmission with explanation tied to the chosen scope

Pre-Resubmission Verification

Phase 1: Quick Health Check (15 min)

Run automated audit:

npm run ads-readiness-assessment --site-url https://example.com

Review scores:

Overall score ≥70/100
Score mode declared in the report
No Critical issues
<5 High priority issues (and documented as acceptable)

Phase 2: Original Issue Re-Audit (30 min)

For each rejection reason, verify fix:

If rejected for "Low-Value Content":

If rejected for "Poor UX":

If rejected for "Policy Issues":

If rejected for "Technical Issues":

Phase 3: Spot Checks (20 min)

Test each category manually:

Content:

Read 3 random pages (not your best ones)
Check they're valuable and original-sounding
Verify metadata (title, description) are unique
Check heading structure

Technical:

UX:

Navigate site like first-time user
Can you easily find about/contact?
Any annoying pop-ups?
Readable text sizes?
Touch-friendly buttons on mobile?

Policy:

Review privacy policy
Spot-check affiliate disclosures (10 pages)
Verify contact info works
No obvious prohibited content

Phase 4: Tool Verification (30 min)

Run all diagnostic tools:

# Full diagnostics
npm run ads-readiness-assessment
npm run content-audit
npm run technical-audit  
npm run ux-compliance-audit
npm run policy-risk-scanner

# Export results
npm run export-reports ./pre-resubmission/

Review Results:

All audits show significant improvement from before
Critical/High issues from original rejection are fixed
No new Critical issues introduced
Score trajectory is positive

Pre-Resubmission Checklist

Absolute Requirements (Must Pass)

Strong Recomm (Should Have)

Content quality score ≥75/100
No thin pages (<300 words) at scale
Unique titles and meta descriptions on all pages
Proper H1-H6 heading structure
Core Web Vitals: LCP <2.5s, CLS <0.1
Schema markup implemented
Author credentials visible
User reviews or testimonials
Social proof (if applicable)

Comparison Report

Create before/after comparison:

# Resubmission Readiness Report

**Score Mode:** Core 79 + Profile
**Primary Site Type:** Blog

## Original Rejection Issues
1. Low-value content (thin pages)
2. Intrusive pop-ups
3. Missing contact information

## Status of Fixes

### Issue 1: Low-Value Content
- **Before**: 30% thin pages, average 180 words
- **After**: 5% thin pages, average 520 words
- **Audit Score**: 45/100 → 82/100
- **Status**: ✅ FIXED

### Issue 2: Intrusive Pop-ups
- **Before**: Full-screen overlay on load
- **After**: Delayed pop-up with clear close button
- **Manual Test**: ✅ PASSED

### Issue 3: Missing Contact
- **Before**: No contact info
- **After**: About page + Contact page + Email form
- **Manual Test**: ✅ PASSED

## Overall Readiness: ✅ READY FOR RESUBMISSION
- Critical Issues: 0
- High Issues: 0
- Medium Issues: 2 (acceptable)
- Score Improvement: +37 points

## Confidence Level: HIGH (85%+)

Red Flags (Don't Resubmit Yet)

⚠️ STOP if any of these are true:

Still have HTTPS disabled
Content audit shows <50% improvement
Policy issues still present (prohibited content)
Pop-ups still showing on page load
Still have >20% thin pages
Technical audit shows new Critical issues
Original rejection reason still apparent
Major design is still broken on mobile
Privacy policy is incomplete

If any red flags present: Go back to improvement guides and fix before resubmitting.

Evidence Documentation

For transparency with Google, document your fixes:

# Recovery Evidence

## Issue: Thin Pages (Original Rejection)

### Evidence of Fixes

#### Example Page 1: /blog/getting-started
- Before: 150 words
- After: 650 words
- URL: https://example.com/blog/getting-started
- Changes: Added step-by-step guide, FAQ, examples

#### Example Page 2: /guides/intro
- Before: 200 words
- After: 480 words
- URL: https://example.com/guides/intro
- Changes: Expanded with detailed explanations and examples

### Scope of Improvements
- 25 pages affected
- Average expansion: +320 words per page
- All now meet 300+ word minimum
- Content quality improved across all pages

### Measurement
- Content-audit before: 45/100
- Content-audit after: 82/100
- Improvement: +37 points (82%)

Resubmission Checklist

Before clicking submit:

Post-Resubmission Timeline

0-3 Days: Usually quick initial review by Google 3-7 Days: Full review period begins 7-14 Days: Decision typically made Up to 30 Days: Possible extended review

Check email and Google Search Console regularly.

If Re-Rejected

If rejected again:

Note the new reason carefully
Determine if it's the same issue or different
Run rejection-root-cause-analysis again
Consider appeal-strategy-builder if issue seems unfair
Create new recovery-action-plan for new issues

Related Skills:

Analyze rejection → rejection-root-cause-analysis
Create plan → recovery-action-plan
Appeal (if disputing) → appeal-strategy-builder

resubmission-readiness-check

Installation

Stronger alternatives

Similar popular skills

Also in this package

Agent compatibility

Repository health

Package contents

History

SKILL.md