Next.js + WordPress SEO Optimization
Budget: €30 – €250 EUR
Technical Specification – SEO Audit and Optimization – Next.js + WordPress Headless
Primary Objective
Ensure that all critical pages (especially articles) are properly Server-Side Rendered (SSR).
Without full SSR:
Googlebot and other crawlers cannot properly crawl or index the site.
Critical SEO content (titles, text, images) will not be visible to search engines.
The overall SEO performance of the website will be severely impacted.
The delivered HTML must include all critical visible content without requiring JavaScript execution.
Scope of Work
1. Server-Side Rendering Verification (highest priority)
Confirm that all key pages, especially article pages, are fully server-side rendered.
When the page is requested (by a browser or crawler with JavaScript disabled), the returned HTML must include:
Proper <title> and <meta description> tags
Full textual content
Images with alt attributes
There must be no empty divs or placeholders relying only on client-side hydration.
HTML output must be fully populated at first server response.
2. JavaScript Disabled Test
Simulate browsing the site with JavaScript disabled (or use a non-JS crawler).
Verify that critical content (titles, paragraphs, images) is still visible and accessible.
Identify and fix any areas where content relies exclusively on client-side rendering for SEO-critical information.
3. SEO Accessibility and Indexing
Check if Googlebot can access and index the pages properly (via Google Search Console and external SEO crawlers).
Investigate causes of non-indexed articles:
Server-side rendering issues
Wrong meta robots or canonical tags
Blocks caused by robots.txt or HTTP headers
4. Technical SEO Standards Compliance
Verify the correct dynamic generation of:
<title> for each page
<meta description> for each page
<link rel="canonical"> with correct URLs
Structured data (JSON-LD), especially for article content, if applicable
Confirm that Open Graph (og:) and Twitter Card metadata are properly generated.
5. Sitemap and Robots.txt
Ensure that the XML sitemap is properly generated, accessible, and includes all critical pages.
Verify that robots.txt does not block any SEO-critical pages.
6. Core Web Vitals and Performance
Evaluate Core Web Vitals (LCP, FID, CLS) for key pages.
Provide recommendations for performance improvements if any bottlenecks are found.
Non-Negotiable Requirements
Each important page must deliver a fully populated HTML version on first server load.
No critical page should rely solely on JavaScript execution to render SEO-important content.
Article pages must be crawlable, indexable, and visible to Google without rendering issues.
Expected Deliverables
A synthetic audit report listing detected issues and applied corrections.
A clear list of pages and areas that were fixed or optimized.
Additional technical SEO recommendations if needed.
Primary Objective
Ensure that all critical pages (especially articles) are properly Server-Side Rendered (SSR).
Without full SSR:
Googlebot and other crawlers cannot properly crawl or index the site.
Critical SEO content (titles, text, images) will not be visible to search engines.
The overall SEO performance of the website will be severely impacted.
The delivered HTML must include all critical visible content without requiring JavaScript execution.
Scope of Work
1. Server-Side Rendering Verification (highest priority)
Confirm that all key pages, especially article pages, are fully server-side rendered.
When the page is requested (by a browser or crawler with JavaScript disabled), the returned HTML must include:
Proper <title> and <meta description> tags
Full textual content
Images with alt attributes
There must be no empty divs or placeholders relying only on client-side hydration.
HTML output must be fully populated at first server response.
2. JavaScript Disabled Test
Simulate browsing the site with JavaScript disabled (or use a non-JS crawler).
Verify that critical content (titles, paragraphs, images) is still visible and accessible.
Identify and fix any areas where content relies exclusively on client-side rendering for SEO-critical information.
3. SEO Accessibility and Indexing
Check if Googlebot can access and index the pages properly (via Google Search Console and external SEO crawlers).
Investigate causes of non-indexed articles:
Server-side rendering issues
Wrong meta robots or canonical tags
Blocks caused by robots.txt or HTTP headers
4. Technical SEO Standards Compliance
Verify the correct dynamic generation of:
<title> for each page
<meta description> for each page
<link rel="canonical"> with correct URLs
Structured data (JSON-LD), especially for article content, if applicable
Confirm that Open Graph (og:) and Twitter Card metadata are properly generated.
5. Sitemap and Robots.txt
Ensure that the XML sitemap is properly generated, accessible, and includes all critical pages.
Verify that robots.txt does not block any SEO-critical pages.
6. Core Web Vitals and Performance
Evaluate Core Web Vitals (LCP, FID, CLS) for key pages.
Provide recommendations for performance improvements if any bottlenecks are found.
Non-Negotiable Requirements
Each important page must deliver a fully populated HTML version on first server load.
No critical page should rely solely on JavaScript execution to render SEO-important content.
Article pages must be crawlable, indexable, and visible to Google without rendering issues.
Expected Deliverables
A synthetic audit report listing detected issues and applied corrections.
A clear list of pages and areas that were fixed or optimized.
Additional technical SEO recommendations if needed.