Site Analysis

Site analysis is the foundation of Rampify's SEO intelligence. It discovers all your pages, checks their health, and identifies issues that need attention.

How It Works#

When you trigger a site analysis, Rampify:

  1. Discovers pages from your sitemap (or crawls your navigation)
  2. Checks each URL for technical SEO elements
  3. Detects issues automatically based on severity rules
  4. Updates your dashboard with fresh data

Running an Analysis#

Manual Analysis#

Click "Analyze Site Now" from your site's overview page to trigger an immediate scan.

The analysis typically takes 1-3 minutes depending on your site size:

  • Small sites (< 50 pages): ~30 seconds
  • Medium sites (50-500 pages): 1-2 minutes
  • Large sites (500+ pages): 2-5 minutes

Scheduled Analysis (Starter+)#

On the Starter tier and above, you can configure automatic scheduled crawls:

  • Daily - Best for frequently updated sites (blogs, news)
  • Weekly - Good for most business sites
  • Monthly - Suitable for static marketing sites

Configure schedules in Settings → Crawling.

Discovery Methods#

Sitemap Discovery (Preferred)#

Rampify automatically finds your sitemap by checking:

  1. /sitemap.xml - Standard location
  2. /sitemap_index.xml - Sitemap index
  3. /robots.txt - Sitemap directives
  4. Common CMS patterns (WordPress, Next.js, etc.)

Benefits:

  • Fast and comprehensive
  • Respects your sitemap priority
  • Handles sitemap indexes automatically
  • No server load from crawling

Navigation Crawling (Fallback)#

If no sitemap is found, Rampify falls back to navigation crawling:

  • Starts at your homepage
  • Follows internal links up to 3 levels deep
  • Limited to 100 pages (configurable)
  • Respects robots.txt rules

When to use:

  • Sites without sitemaps
  • Testing/staging environments
  • Small sites (< 50 pages)

What Gets Checked#

For each URL, Rampify checks:

HTTP Status#

  • 200 OK - Page is accessible
  • 301/302 - Redirects (chain tracking)
  • 404 - Page not found (critical issue)
  • 5xx - Server errors (critical issue)

Response Time#

  • Measures page load speed
  • Flags pages slower than 3 seconds
  • Tracks response time trends

Meta Elements#

Title Tag:

  • Presence check
  • Length validation (50-60 characters optimal)
  • Uniqueness across site

Meta Description:

  • Presence check
  • Length validation (150-160 characters optimal)
  • Uniqueness across site

Schema.org Markup#

Detects structured data types:

  • JSON-LD - Recommended format
  • Microdata - Legacy format
  • RDFa - Legacy format

Common types detected:

  • Organization
  • Article
  • Product
  • BreadcrumbList
  • WebSite
  • FAQPage

Redirect Chains#

Tracks complete redirect paths:

example.com/old-page
  → example.com/temp-redirect (301)
  → example.com/new-page (200)

Flags chains longer than 2 redirects as warnings.

Page Size#

Measures total page weight including:

  • HTML markup
  • Inline CSS/JavaScript
  • Embedded images (data URIs)

Flags pages larger than 5MB.

Issue Detection#

Issues are automatically categorized by severity:

Critical Issues#

Require immediate attention:

  • 404 errors - Broken pages
  • 5xx errors - Server problems
  • Infinite redirect loops
  • Timeout errors

Warnings#

Optimization opportunities:

  • Missing title tags
  • Long redirect chains (> 2 hops)
  • Slow response times (> 3 seconds)
  • Large page sizes (> 5MB)

Info#

Informational items (not highlighted in UI):

  • Missing meta descriptions - Suboptimal but not critical
  • No robots.txt - Optional file
  • No Schema.org markup - Enhancement opportunity

Analysis Results#

Site Overview#

After analysis completes, view:

  • Total URLs discovered
  • HTTP status breakdown (200s, 301s, 404s, etc.)
  • Issues by severity (critical, warning, info)
  • Average response time
  • Technology detected (CMS, hosting, CDN)

URL Table#

Browse all discovered pages with:

Filters:

  • HTTP status (200, 301, 404, etc.)
  • Issue type (missing title, slow response, etc.)
  • Sitemap presence (in sitemap vs crawled)

Sorting:

  • Status code
  • Response time
  • Last checked date
  • Alphabetical (A-Z)

Details:

  • Click any URL to see full check history
  • View redirect chains
  • See detected Schema.org types
  • Track changes over time

Issues Tab#

See all issues grouped by severity:

  • Critical (red badge) - Immediate action required
  • Warning (yellow badge) - Should be fixed soon
  • Info (blue badge) - Nice to have

For each issue:

  • First detected - When the issue first appeared
  • Last detected - Most recent occurrence
  • Status - Open, acknowledged, resolved, ignored
  • Notes - Add context or track fixes

Logo Extraction#

During analysis, Rampify automatically:

  1. Extracts your logo from homepage
  2. Detects background color for proper display
  3. Allows customization via color picker

Found in these locations (in order):

  • Open Graph image (og:image)
  • Schema.org logo
  • <link rel="icon"> or favicon
  • First prominent image

Technology Detection#

Rampify identifies:

Content Management Systems:

  • WordPress
  • Webflow
  • Shopify
  • Next.js
  • Astro
  • Ghost

Hosting Providers:

  • Vercel
  • Netlify
  • AWS
  • Google Cloud
  • Cloudflare Pages

CDN Services:

  • Cloudflare
  • Fastly
  • CloudFront
  • Akamai

Analysis History#

View past analyses in Site Check History:

  • Date and time of each check
  • URLs discovered
  • Issues found
  • Duration
  • Status (completed, failed, in progress)

Compare analyses over time to:

  • Track issue resolution
  • Identify new problems
  • Monitor site growth
  • Measure performance trends

Best Practices#

When to Run Analysis#

Immediately after:

  • Site redesign or migration
  • Major content updates
  • CMS upgrades
  • Server changes

Regularly:

  • Daily (for frequently updated sites)
  • Weekly (for most sites)
  • Monthly (for static sites)

Improving Analysis Speed#

Optimize your sitemap:

  • Remove unnecessary URLs
  • Use sitemap indexes for large sites
  • Keep lastmod dates current

Server optimization:

  • Enable compression (gzip/brotli)
  • Implement caching headers
  • Use a CDN for static assets

Handling Large Sites#

For sites with 1,000+ pages:

  1. Use sitemap indexes to organize by section
  2. Enable incremental crawling (Pro tier)
  3. Exclude non-SEO pages (admin, search results)
  4. Configure crawl rate limiting to avoid server load

Troubleshooting#

"No sitemap found"#

Cause: Sitemap not in standard location

Solutions:

  • Manually enter sitemap URL in site settings
  • Add sitemap directive to robots.txt
  • Generate sitemap (most CMSs do this automatically)

"Analysis timed out"#

Cause: Too many URLs or slow server responses

Solutions:

  • Optimize server response times
  • Reduce URLs in sitemap
  • Upgrade to higher tier for longer timeouts

"Connection refused"#

Cause: Firewall or hosting restrictions

Solutions:

  • Whitelist Rampify's IP addresses
  • Check server firewall rules
  • Verify domain DNS is resolving correctly

Next Steps#