Technical SEO

🔁 Redirects

🔍 Using Search Atlas with Noindex Staging Sites

🚧 Understanding the Noindex Constraint If your staging site uses a noindex directive (for example, via a robots.txt disallow rule or a noindex meta tag), Search Atlas tools that rely on automated crawling — including Site Audit and content imports in Content Genius — cannot access or process that site. This is not a platform limitation you can work around with settings; it is a deliberate crawl block that prevents any crawler, including Search Atlas, from reading your pages. This means that if your rebuilt site is live at a staging subdomain such as beta.snazzy.solutions but is set to noindex, the automated workflows described in some help resources will not work until the noindex restriction is lifted. ✅ What You Can and Cannot Do It helps to know exactly where the boundary is before choosing a workflow: - Cannot do: Run a Site Audit crawl against a noindex staging subdomain. - Cannot do: Auto-import staging pages into Content Genius via URL crawl. - Can do: Paste page content manually into Content Genius for AI-powered feedback. - Can do: Use Content Genius to audit and optimise individual pages by entering copy directly. - Can do: Run a full Site Audit and content review once the site is live and indexable, or once the noindex restriction is temporarily removed in a controlled way. 📋 Option 1 — Manual Content Review in Content Genius This is the recommended approach when your staging site is noindex and you need pre-launch feedback on page quality, SEO signals, and content gaps. 1. Open Search Atlas and navigate to Content → Content Genius (What are we writing today?). 2. Create a new document or open an existing one. 3. Copy the text content from your staging page (title, headings, body copy, meta description). 4. Paste the content into the Content Genius editor. 5. Enter your target keyword and configure the settings as you would for any new piece of content. 6. Use the AI suggestions, content score, and NLP recommendations to identify gaps and improvements. 7. Repeat this process for each key page you want to review before launch. While this approach requires more manual effort than an automated crawl, it gives you detailed, per-page feedback that is fully actionable before the site goes live. 🛠️ Option 2 — Temporarily Remove Noindex for Crawling If your team can safely control access to the staging environment, you may choose to temporarily remove the noindex directive to allow a Site Audit crawl. Use this option only if your staging subdomain is password-protected or otherwise not publicly discoverable, so that search engines do not accidentally index incomplete content. 1. Work with your developer to remove or disable the noindex rule on the staging subdomain. 2. Ensure the subdomain is protected by HTTP authentication or IP restriction so it remains inaccessible to search engine bots during this window. 3. In Search Atlas, go to OTTO SEO → Site Audit in the left sidebar and add your staging subdomain as a new project. 4. Run the audit and review all flagged issues — broken links, missing meta tags, heading structure, page speed signals, and more. 5. Export or document the findings, then restore the noindex directive on the staging site before making anything public. 6. Apply all fixes to the staging build before your production launch. This option gives you the full power of Site Audit but requires coordination with your development team and careful access controls. 🚀 Option 3 — Run a Full Audit Post-Launch If neither manual review nor temporary crawl access is practical before launch, the most straightforward path is to launch the site, confirm indexing is enabled, and then immediately run a Site Audit in Search Atlas. 1. Before going live, make sure all noindex directives are removed from production pages you want indexed. 2. After launch, go to OTTO SEO → Site Audit in the left sidebar and create a new project using your live production domain. 3. Run the audit within the first day of launch to catch and fix any technical issues before they affect rankings. 4. Use Content Genius to review and optimise priority pages using the live URLs once they are crawlable. Pairing a fast post-launch audit with pre-launch manual reviews in Content Genius gives you strong coverage at both stages. ⚡ Quick Reference — Which Workflow Fits Your Situation - Need feedback now, site is noindex: Use manual copy-paste into Content Genius (Option 1). - Can protect staging with a password and remove noindex temporarily: Run Site Audit on staging (Option 2). - Launch is imminent and no access changes are possible: Plan a same-day post-launch audit (Option 3). 💬 Need Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🗺️ Disabling URL Types in Sitemap Settings

🔍 Overview When you import sitemap settings from a plugin like Yoast SEO, Search Atlas does not automatically carry over your exclusion rules. URL types that were disabled in Yoast — such as author pages, video pages, category pages, and tag pages — may appear as enabled in Search Atlas and surface as sitemap errors. This article explains how to locate and disable those URL types directly inside Search Atlas. ⚙️ How Sitemap URL Type Settings Work in Search Atlas Search Atlas manages its own sitemap configuration independently of any third-party SEO plugin. Even if a URL type was excluded in Yoast before migration, Search Atlas may not reflect those exclusions automatically. You will need to review and update these settings after any import or plugin migration. 🛠️ How to Disable Specific URL Types 1. Log in to your Search Atlas account and make sure the correct project (website) is selected. 2. Navigate to the sitemap settings area within your project. If you are unsure where to find this, reach out to our support team for exact navigation steps — the location may vary depending on your account setup. 3. Locate the URL type controls for your sitemap. You should see options corresponding to different URL types that Search Atlas can include — such as posts, pages, categories, tags, authors, and video sitemaps. 4. Find the URL type you want to exclude (e.g., Author, Category, Tag, or Video). 5. Disable or turn off that URL type using the available control. 6. Repeat for each URL type you want to exclude. 7. Save your changes so that the excluded URL types are removed from your sitemap. 📋 Common URL Types to Disable After a Yoast Migration If you previously excluded any of the following in Yoast, check each one in your Search Atlas sitemap settings and disable as needed: - Author pages — Archive pages automatically generated for each author on your site. - Category pages — Taxonomy archive pages for post categories. - Tag pages — Taxonomy archive pages for post tags. - Video sitemap — A separate sitemap index for video content embedded on your pages. Leaving these enabled when they were previously excluded can cause sitemap errors and may send search engines to thin or duplicate content pages, which can negatively affect your crawl budget and indexing. ✅ Verifying Your Sitemap After Changes After saving your updated settings, it is good practice to verify that the excluded URL types no longer appear in your sitemap. You can do this by: - Opening your sitemap URL directly in a browser (e.g., yourdomain.com/sitemap.xml) and confirming the excluded URL types are not listed. - Using the sitemap preview or validation tools available within Search Atlas to confirm the updated sitemap reflects your changes. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

🤖 Noindex & Robots.txt Without Backend Access

🔍 Understanding the Problem When OTTO SEO is implemented through Google Tag Manager (GTM) rather than the WordPress plugin, you may not have direct access to the website's backend or server files. This means you cannot edit the robots.txt file or add meta tags directly to page templates. This article explains your available options for managing crawl directives in this scenario. ⚠️ Important Limitations to Know First Before choosing a method, understand these key constraints: - robots.txt requires server or hosting access. Without backend access, you cannot directly edit this file. - JavaScript-injected noindex tags (via GTM) are not reliable. Search engine crawlers may not execute JavaScript before deciding whether to index a page, so injecting a noindex meta tag through GTM is not a recommended or dependable method. - OTTO deployed via GTM does not control server-level directives such as X-Robots-Tag HTTP headers or robots.txt entries. - robots.txt Disallow ≠ noindex. Disallowing a URL in robots.txt prevents crawling but does not remove an already-indexed page from search results. A noindex meta tag or X-Robots-Tag header is required for de-indexing. ✅ Recommended Options When You Lack Backend Access Use one of the following approaches depending on what access you do have: 1. Request access from the client's developer or hosting provider. This is the most reliable path. Ask the client to grant you access to edit the robots.txt file via their hosting control panel (e.g., cPanel, Kinsta, WP Engine dashboard) or ask their developer to implement the directives on your behalf. 2. Use Google Search Console to manage indexing. If you have Google Search Console access for the property, you can use the URL Inspection tool to request removal of specific URLs. Note that this is a temporary fix (valid for approximately six months) and is not a substitute for a proper noindex directive. 3. Ask the client to add an X-Robots-Tag HTTP header. This is a server-level solution that functions identically to a noindex meta tag. The client's developer or hosting provider can configure this in the server settings (e.g., Apache .htaccess or Nginx config) without requiring changes to individual page templates. This is the preferred technical alternative when robots.txt and meta tags are both inaccessible. 4. Ask the client's developer to add a noindex meta tag to the page template. If GTM is already implemented, the developer clearly has some site access. Coordinate with them to add <meta name="robots" content="noindex"> directly inside the <head> of the relevant page templates. This is more reliable than injecting it through GTM. 🛠️ What OTTO Can and Cannot Do in GTM Mode It is important to set accurate expectations with your client about OTTO's capabilities when deployed via GTM: - OTTO via GTM can: Inject structured data, update meta titles and descriptions, and make on-page content optimisations that do not require server-level access. - OTTO via GTM cannot: Edit robots.txt, set X-Robots-Tag HTTP headers, or reliably control indexing through JavaScript-injected meta tags. - For full OTTO functionality — including robust robots directives management — the WordPress plugin installation is strongly recommended wherever possible. 📋 Steps to Coordinate With Your Client 1. Identify which pages or sections need to be blocked from indexing. 2. Determine what level of access is available: hosting panel, server config, CMS backend, or developer contact. 3. Share the appropriate directive with whoever has access — either the robots.txt rule, the X-Robots-Tag header configuration, or the noindex meta tag snippet. 4. After changes are implemented, verify them using the URL Inspection tool in Google Search Console or a third-party robots.txt tester. 5. Monitor Search Atlas to confirm OTTO is no longer flagging those pages as indexable. 💡 Pro Tips - Always confirm whether you are working on a subdomain — subdomains require their own separate robots.txt file. A robots.txt on the root domain does not automatically apply to subdomains. - If the site has both HTTP and HTTPS versions or www and non-www variants, ensure the correct canonical version is covered by your directives. Robots.txt rules apply per protocol and per subdomain. - After any robots.txt or noindex change, allow several days to weeks for Google to re-crawl and reflect the update in search results. 💬 Need Further Help? If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team. Additional Notes To get the fastest resolution, have ready: project name and domain, OTTO implementation method, description of goal (noindex/robots.txt/removal), specific pages/URL patterns, current backend/CMS access level, and any error messages with timestamps.

🗺️ Managing Sitemap URL Exclusions in Search Atlas

Overview When migrating from Yoast SEO to Search Atlas, you may notice that URL types you previously excluded from your sitemap — such as author pages, video pages, category pages, and tag pages — appear re-enabled in Search Atlas. This happens because Search Atlas maintains its own independent sitemap settings, and Yoast's exclusion rules do not carry over automatically. This article explains the current sitemap exclusion options available in Search Atlas, how they compare to Yoast, and what steps you can take right now to manage your sitemap effectively. How Search Atlas Sitemap Settings Work Search Atlas generates your sitemap automatically based on your site's content. You can access your sitemap settings inside the Search Atlas platform to view which URLs are currently included and make adjustments. It is important to understand that Search Atlas and Yoast approach sitemap configuration differently: - Yoast SEO allows you to disable entire URL types globally — for example, turning off all author archives, all tag pages, or all category pages with a single toggle. - Search Atlas currently focuses on URL-level and page-level controls rather than broad post-type or taxonomy-level exclusions. These controls are accessible in your WordPress admin panel under Search Atlas → Settings, where you can find options to include or exclude individual URL types such as post types and taxonomies. This means that after migrating, URL types that were globally suppressed in Yoast will not automatically carry over as excluded in Search Atlas. When you install Search Atlas and disable or remove Yoast, Search Atlas generates a fresh sitemap based on its own default settings — not Yoast's saved preferences. Those pages may reappear in your sitemap and, in some cases, surface with crawl errors, particularly if those pages return non-200 status codes or have other issues. What You Can Do Right Now While bulk post-type exclusion toggles are not yet available as a self-serve feature, there are practical steps you can take to reduce unwanted URLs in your sitemap: 1. Audit your sitemap errors: Log in to Search Atlas and navigate to your sitemap settings. Review any URLs flagged with errors and prioritise fixing or removing pages that should not be indexed. 2. Use noindex on unwanted page types: For author pages, tag archives, or category pages you do not want indexed, apply a noindex meta directive to those templates. Search Atlas respects noindex signals, so these pages will not pass SEO value. 3. Remove individual URLs: Where a specific URL is causing errors and should not appear in the sitemap, check whether your sitemap settings allow you to exclude it at the individual URL level. 4. Check your WordPress settings: For category, tag, and author archives, WordPress itself offers visibility controls. Setting these archives to noindex at the WordPress level helps ensure Search Atlas does not treat them as indexable pages. If you are unsure which steps apply to your setup or need help confirming what sitemap controls are available in your account, reaching out to the support team is the fastest way to get accurate guidance for your specific configuration. When you do, please have the following ready: - Your site URL - The specific URL types you want to exclude (e.g. author pages, category pages, tag pages, video pages) - The Search Atlas plugin version you have installed - A note of any crawl errors you are seeing related to the excluded URL types Yoast vs. Search Atlas: Feature Comparison - Global post-type exclusion toggle: Available in Yoast — not yet available as a self-serve option in Search Atlas. - Individual URL exclusion: Available in Search Atlas at the page level. - Noindex support: Respected by both Yoast and Search Atlas. - Automatic sitemap generation: Both tools generate sitemaps automatically based on your site's content. Recommended Settings After Migrating From Yoast To replicate your previous Yoast exclusions as closely as possible, review each of the following URL types and disable any that you had turned off in Yoast: - Author archive pages — commonly disabled on single-author sites to avoid duplicate content. - Category and tag archive pages — often excluded when they hold thin or duplicate content. - Video sitemaps — disable if you do not host video content or use a dedicated video sitemap plugin. - Custom post types — exclude any custom post types that should not be indexed or surfaced in search. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

What Are Core Web Vitals? (+4 Tips for Improvement)

When it comes to Search Engine Optimization (SEO), Google’s Core Web Vitals are a make-or-break ranking factor. Unlike many other SEO metrics, these measure your website’s performance from the user’s perspective — focusing on speed, responsiveness, and visual stability. Core Web Vitals were designed to make websites faster, more enjoyable, and more user-friendly. Optimizing them not only improves SEO rankings but also enhances your visitors’ overall experience and your business’s conversion rates. ⚙️ What Are Core Web Vitals? Just like a doctor checks a patient’s key vitals to gauge health, Google’s Core Web Vitals give insight into a website’s “usability health.” They’re made up of three key metrics: - Largest Contentful Paint (LCP) - Cumulative Layout Shift (CLS) - First Input Delay (FID) 📊 Why Did Google Develop Core Web Vitals? Google realized many top-ranking sites provided relevant content but poor usability. To fix this, it introduced Core Web Vitals — a standardized way to measure user experience across all websites and content management systems. When Core Web Vitals launched, 98% of top-ranking sites failed to meet the new standards. By focusing on these metrics, Google hopes to improve the overall health of the web ecosystem, benefiting developers, users, and platforms like WordPress or Shopify. 🧩 Breaking Down LCP, CLS, and FID Largest Contentful Paint (LCP) Measures how long it takes for the largest visible element (like a featured image or heading) to load. - Ideal Time: Under 2.5 seconds - Why It Matters: Slow load times increase bounce rates and can hurt conversions. Cumulative Layout Shift (CLS) Tracks how often visual elements shift unexpectedly during page load. - Ideal Time: Under 0.1 seconds - Why It Matters: Layout shifts frustrate users and lead to misclicks or abandoned sessions. First Input Delay (FID) Measures how long it takes for a page to respond after the user first interacts (click, tap, type, etc.). - Ideal Time: Under 100 milliseconds - Why It Matters: Delays reduce interactivity and can cause users to leave the page. 🔎 Why Core Web Vitals Matter for SEO Google uses Core Web Vitals as an official ranking signal. Poor performance in these metrics can negatively impact visibility in search results, bounce rate, and brand reputation. Just like in a physical store, a bad first impression online can drive visitors away. Improving your Core Web Vitals leads to better rankings, user engagement, and conversion rates. 🛠️ How to Audit Your Website’s Core Web Vitals Option 1: Lighthouse (Google Chrome) 1. Open Chrome in Incognito mode. 2. Visit your website. 3. Right-click and select Inspect → choose the double-arrow icon → Lighthouse. 4. Click Generate report and choose device type (mobile or desktop). 5. Review “Total Blocking Time” in place of FID. Option 2: PageSpeed Insights 1. Go to PageSpeed Insights. 2. Enter your URL and click Analyze. 3. Review the color-coded Web Vitals (red, orange, green). 4. Expand each section for optimization suggestions. Option 3: Search Atlas Dashboard If you’re a Search Atlas user: 1. Open your GSC Insights tool. 2. Select a page and click Page Insights. 3. Review Historical Data and Core Web Vitals status directly in the dashboard. 🚀 4 Tips for Improving Core Web Vitals 1. Know your numbers and set goals: Use Search Atlas, Lighthouse, or Google Search Console to identify common issues and automate fixes (e.g., image compression). 2. Review real-user data frequently: Monitor reports regularly and after updates to ensure site changes don’t harm performance. 3. Identify and optimize your LCP: Use the Performance tab to find your LCP element, then compress or optimize it. 4. Use Content Delivery Networks (CDNs): Improve speed for global users by serving content from servers closer to their locations. ✅ Final Thoughts on Core Web Vitals Core Web Vitals measure how enjoyable your site is for users — by tracking loading times, interactivity, and visual stability. They’re key for both SEO performance and conversion optimization. These metrics are here to stay, and improving them ensures your website stays visible, competitive, and user-friendly. If you need help optimizing for Google’s Core Web Vitals, our technical SEO specialists are here to assist.

🗺️ An Easy Guide: How to Create a Sitemap for Google

Creating an optimized sitemap is crucial to improving your website’s search engine visibility and user experience. Keep reading to explore how to create, optimize, and submit a sitemap for Google — plus answers to common questions. 🔍 What is a Sitemap and Why is it Important? A sitemap is an XML file that gives search engines like Google a roadmap of your website’s content. It lists your site’s URLs in a structured hierarchy, helping search engines: - Understand your site layout - Discover new or updated pages - Prioritize which content to index When optimized correctly, sitemaps: - Improve your visibility in search results - Ensure important pages aren’t missed - Enhance site navigation for users A well-built sitemap also helps improve your site’s SEO performance by ensuring crawlers can efficiently access all relevant pages. 🤖 Sitemap vs. Robots.txt: Understanding the Difference While both are key SEO files, they serve different purposes: File Purpose Sitemap Lists URLs you want indexed by search engines robots.txt Tells crawlers which URLs to avoid You can also include your sitemap’s location inside your robots.txt file to make it easier for crawlers to find. 🧩 XML and Sitemaps: Why XML Format Matters XML (Extensible Markup Language) is the standard format for sitemaps. It’s machine-readable and ensures search engines can: - Interpret your content efficiently - Crawl your site’s structure accurately - Index new or changed pages quickly 🗂️ Different Types of Sitemaps There are several sitemap formats depending on your content type: Sitemap Type Description XML Sitemap Standard format for search engine crawlers HTML Sitemap Human-friendly version for users Video Sitemap Helps index video content Image Sitemap Focuses on image indexing News Sitemap For fast indexing of news content For SEO purposes, XML sitemaps are the most important since they communicate directly with Google. 🧱 Steps to Create a Sitemap for Google ✅ Using the Yoast Plugin (WordPress) The Yoast SEO plugin automates sitemap creation: 1. Install and activate Yoast SEO. 2. Go to Yoast SEO → General → Features tab. 3. Enable XML Sitemaps. 4. Click Save Changes to generate your sitemap automatically. Yoast is also compatible with platforms like Shopify, Squarespace, and BigCommerce (though not all support full integration). 🧰 Creating a Sitemap in Google Search Console Google no longer provides a generator, but you can submit sitemaps there: 1. Log into Google Search Console. 2. Select your property. 3. Navigate to Sitemaps → Add a new sitemap. 4. Enter your sitemap URL (e.g. https://example.com/sitemap.xml). 5. Click Submit. 🕷️ Using Screaming Frog SEO Spider A great option for non-WordPress sites: 1. Open Screaming Frog SEO Spider. 2. Go to Sitemaps → + New Sitemap. 3. Choose which pages to include. 4. Export the file as XML. 5. Upload it to your website’s root directory. 💻 Manually Creating a Sitemap If you’re comfortable with code, you can build your sitemap manually: 1. Open a text editor. 2. Add URLs using the following XML tags: <url> <loc>https://example.com/page</loc> <lastmod>2025-10-20</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> 3. Save as sitemap.xml. 4. Upload to your root directory via CMS or FTP. Update your sitemap each time new pages are added. ⚠️ Common Sitemap Mistakes (and How to Avoid Them) Mistake Fix Omitting important pages Include all key pages, even if not linked in the main menu Outdated sitemaps Update regularly as content changes Wrong format Use proper XML syntax Too many URLs Limit to 50,000 URLs per sitemap Broken links Use tools like Search Atlas or Screaming Frog to detect and fix issues 💡 Sitemap Optimization Tips To get the most out of your sitemap: - Use clear, keyword-rich titles and meta descriptions - Set priority tags (<priority>) for key pages - Add update frequency (<changefreq>) for frequently updated content - Include image or video sitemaps for media-heavy sites - Re-submit your sitemap in Google Search Console after major site changes 🚀 Why Submit a Sitemap to Google? Submitting a sitemap: - Helps Google discover and index pages faster - Communicates crawl priority and last update date - Reduces the risk of orphaned pages being missed - Strengthens visibility for new and updated content 📈 How to Check Sitemap Performance In Google Search Console: 1. Go to Sitemaps → Submitted sitemaps. 2. Review crawl stats, errors, or warnings. 3. Fix issues, update your sitemap, and re-submit. You can also use Search Atlas, Ahrefs, or SEMrush for deeper analysis of indexed URLs and crawl frequency. 🔌 Plugins and Tools for Sitemap Creation Tool Platform Key Features Yoast SEO WordPress Auto-generates XML sitemaps Google XML Sitemaps WordPress Submits automatically to Google WP Sitemap Page WordPress Create visual sitemaps for users Screaming Frog SEO Spider Multi-platform XML export and crawl analysis XML-Sitemaps.com Any Free web-based generator 🧩 Troubleshooting Sitemap Issues Standard solutions for sitemap problems: - Verify URLs — fix broken or redirected links - Check file size — keep under 50MB - Update robots.txt — ensure it references your sitemap - Avoid noindex pages — exclude blocked or private URLs Google Search Console will automatically alert you to these issues. 🔄 Keeping Your Sitemap Up to Date Regular updates ensure Google crawls your most accurate content. Automated plugins or CMS integrations (like Yoast or Rank Math) can update sitemaps dynamically whenever you add new pages or posts. 🧠 Additional Tips for Effective SEO - Use canonical tags to prevent duplicates - Include only valuable, high-quality pages - Add structured data (schema) where applicable A clean, current sitemap supports both SEO health and user experience. 🏁 Closing Notes An optimized sitemap acts as the blueprint of your website — guiding both users and search engines through your content. Key Takeaways: - Always use XML format for Google. - Keep it current and error-free. - Submit via Google Search Console. - Use automation tools when possible. 🧭 The easier it is for Google to crawl your website, the easier it is for your audience to find it.

🗺️ XML Sitemap Guide

Use the Search Atlas WordPress plugin — or any of four standard methods — to create, optimize, and submit an XML sitemap that helps Google discover and index every page on your site. 📘 What Is a Sitemap? A sitemap is an XML file that acts as a roadmap for search engine crawlers. It lists all the important pages of your website and provides structure signals so Google understands how your content is organized and which pages matter most. Think of it as directions for web crawlers — helping them discover, crawl, and index every page efficiently, even those not easily accessible from your main navigation. 💡 What Is XML? XML (Extensible Markup Language) is the format that web crawlers "speak." It structures information in a way that's readable by both humans and machines. Sitemaps written in XML tell search engines which URLs exist, when they were last updated, and how they relate to other pages. 🤖 How Web Crawlers Use a Sitemap Crawlers use sitemaps to: - Find new pages that have been added recently - Discover unlinked or orphaned pages - Understand the hierarchy and importance of different URLs This ensures all relevant pages get indexed quickly and correctly. 📑 Types of Sitemaps Supported The Search Atlas WordPress plugin supports three sitemap types, each suited to different content: - General Sitemap — Covers standard pages, posts, and custom post types. Use this for most websites. - News Sitemap — Designed for time-sensitive news content. Helps Google News discover and index articles quickly. - Video Sitemap — Highlights video content and provides metadata such as duration, thumbnail, and description to improve video search visibility. 🔢 How Many URLs Can Be in a Sitemap? A single sitemap file supports up to 50,000 URLs with a maximum uncompressed file size of 50 MB. For larger sites, create multiple sitemap files and connect them with a sitemap index file. 📈 Why Sitemaps Matter for SEO A properly optimized sitemap helps: - Improve crawl efficiency and indexation rates - Strengthen site structure visibility for Google - Speed up discovery of new or recently updated pages, reducing the gap between publishing and indexing - Prevent pages from being missed or ignored by crawlers If your site structure is disorganized, Google may struggle to index all your pages — leading to lost rankings and missed traffic. ⚙️ Sitemap vs. Robots.txt - Sitemap — Lists all URLs you want search engines to index - robots.txt — Tells crawlers which URLs they can or cannot access Tip: Include your sitemap URL in your robots.txt file for easier discovery. 🗂️ Where Your Sitemap Lives Place your sitemap in your website's root directory — for example: https://yourdomain.com/sitemap.xml This is where Google expects to find it, and where you'll upload it via your CMS or hosting panel. ✅ Why You Should Submit a Sitemap to Google Submitting a sitemap ensures Google knows about all your important pages and indexes them accurately. Use any of the methods below to create and submit yours. 📝 How to Create a Sitemap for Google Option 1: Yoast SEO (WordPress) 1. Install and activate the Yoast SEO plugin. 2. From your WordPress dashboard, go to Yoast SEO → General. 3. Under the Features tab, find XML Sitemaps. 4. Toggle the setting to Enabled (On). 5. Click Save Changes. Yoast automatically builds and updates your sitemap. This method also works for Shopify, Squarespace, and BigCommerce. Option 2: Google Search Console While Google no longer offers a sitemap generator, you can still submit one easily. 1. Log in to Google Search Console. 2. Add a new property using your URL-prefix. 3. Verify ownership with a Google-approved method. 4. Navigate to Sitemaps in the left menu. 5. Enter your sitemap URL (e.g., sitemap.xml) and click Submit. Option 3: Screaming Frog SEO Spider (Free Version) 1. Download and install Screaming Frog SEO Spider. 2. Open the program and select the Sitemaps tab. 3. Click + New Sitemap, then name and create your file. 4. Run a site crawl. 5. When complete, click Export and save the sitemap as .xml. Option 4: Create Manually 1. Create a plain text file listing all your canonical URLs. 2. Save the file as sitemap.xml. 3. Upload it to your site's root directory (in WordPress, use WP File Manager). This approach gives you full control over your sitemap hierarchy and structure. 🎛️ Filtering Your Sitemap Content (Coming Soon) An upcoming release will give you granular control over which content appears in each sitemap (General, News, and Video): - Post type toggles — Include or exclude specific post types from any sitemap. - Category and tag toggles — Choose which categories and tags are surfaced. - Taxonomy toggles — Manage custom taxonomies independently. - URL exclusion — Exclude individual URLs from any sitemap. These controls apply across all three sitemap types. 🛠️ Troubleshooting: 403 Errors on nginx/Plesk If your sitemap URL returns a 403 Forbidden error on nginx or Plesk servers, update to the latest version of the Search Atlas WordPress plugin. The latest version routes sitemaps through WordPress rewrite rules instead of static file serving, which resolves cases where the web server blocks physical sitemap files. ⚠️ Common Sitemap Mistakes to Avoid - Omitting pages — Include every canonical page you want indexed. - Failing to update — Refresh your sitemap whenever pages change or are added. - Incorrect file format — Always save as .xml. - Unreadable structure — Keep the XML clean and organized. - Too many pages per file — Split large sites into multiple sitemaps (max 50,000 URLs per file). 🔧 How to Optimize Your Sitemap 1. Keep it current: Update whenever new pages are added. 2. Use correct XML format: Required for search engine readability. 3. Include accurate metadata: URL, last modified date, title, and meta description. 4. Use canonical URLs: Avoid duplicate entries. 5. Optimize titles and descriptions: Make them keyword-rich and descriptive. 📤 How to Submit Your Sitemap to Google 1. Log in to Google Search Console. 2. Go to Sitemaps. 3. Click Add a new sitemap. 4. Enter your sitemap URL (e.g., sitemap.xml). 5. Click Submit. You'll see a confirmation once Google processes your sitemap. 🔌 Recommended Sitemap Plugins 1. Yoast SEO — Includes automatic XML sitemap generation. 2. Google XML Sitemaps — Submits to Google and alerts you on updates. 3. WP Sitemap Page — Allows creation of sitemaps for specific posts or pages. 🎯 You now have everything you need to build, optimize, and submit an XML sitemap that keeps Google fully informed about your site — helping more pages get discovered and indexed faster.

⚡ Understanding Core Web Vitals: LCP, INP, and CLS Explained

Core Web Vitals are the three Google metrics — LCP, INP, and CLS — that directly influence search rankings by measuring how real users experience your pages. Understand the thresholds and fixes for each, and you can move any flagged page into the Good range. 📋 What Are Core Web Vitals? Google introduced Core Web Vitals in 2021 as part of the Page Experience Update, measuring real-world user experience across three dimensions: loading speed, responsiveness, and visual stability. In March 2024, Google updated the set by replacing First Input Delay (FID) with Interaction to Next Paint (INP). Together, the three metrics give a comprehensive picture of page quality from the user's perspective — and Google uses them as a ranking signal. ⏱️ Largest Contentful Paint (LCP) What it measures: The time it takes for the largest visible content element — such as a hero image, video, or block of text — to render on screen. - Good: ≤ 2.5 seconds - Needs Improvement: 2.5 – 4.0 seconds - Poor: > 4.0 seconds How to improve LCP - Optimize and compress images. - Serve assets via a CDN. - Add fetchpriority="high" to the LCP image so the browser prioritizes its download. - Minimize render-blocking JavaScript and CSS. - Upgrade hosting if server response times are slow. - Lazy load only images that are below the fold — never the LCP element itself. Important: Do not apply lazy loading to the LCP element (typically the hero image or banner). Lazy loading the largest above-the-fold asset directly worsens LCP. 🖱️ Interaction to Next Paint (INP) What it measures: The latency of all user interactions — clicks, taps, and key presses — throughout the page's lifecycle, reporting the longest interaction observed. INP replaced First Input Delay (FID) as an official Core Web Vital on March 12, 2024. - Good: ≤ 200 milliseconds - Needs Improvement: 200 – 500 ms - Poor: > 500 ms How to improve INP - Break long tasks into smaller chunks to reduce main-thread blocking. - Use scheduler APIs — such as scheduler.yield() or requestIdleCallback — to yield back to the browser during heavy work. - Avoid heavy main-thread work during user interactions. - Remove or defer render-blocking third-party scripts that delay interaction handling. 📐 Cumulative Layout Shift (CLS) What it measures: The sum of all unexpected layout shift scores during a page's entire lifetime — for example, when text moves down because an image loads above it, or a button shifts as an ad slot renders. - Good: ≤ 0.1 - Needs Improvement: 0.1 – 0.25 - Poor: > 0.25 How to improve CLS - Set explicit width and height attributes on all images and videos. - Reserve space for ad slots and embeds before they load. - Avoid inserting content above existing page content after it has loaded. - Use CSS transform animations instead of properties that trigger layout changes. 📊 How to Measure Core Web Vitals Before optimizing, measure. Google tools report two types of data — understand both before acting: - Lab data — simulated measurements in a controlled environment. Useful for debugging, but does not affect ranking. - Field data — real-user measurements collected from actual Chrome visits. This is what Google uses for ranking signals. Use these tools to capture both: - Google Search Console — Core Web Vitals report showing field data grouped by URL pattern. - PageSpeed Insights — Both lab and field data for individual URLs. - Chrome DevTools / Lighthouse — In-browser lab audits for debugging specific pages. - Chrome User Experience Report (CrUX) — Aggregated real-user field data across millions of sites. 🔍 Monitoring Core Web Vitals in Search Atlas You don't need to leave Search Atlas to audit Core Web Vitals. Both Site Audit and the PageSpeed tool surface LCP, INP, and CLS metrics directly for any URL you monitor, so you can spot regressions alongside the rest of your technical SEO data. If you publish with Website Studio, monitor your generated sites' Core Web Vitals scores regularly — especially Mobile PageSpeed — and apply the LCP, INP, and CLS fixes above to any pages flagged as needing improvement. 💡 Best Practice: Test 75% of Your Pages Google recommends that at least 75% of your site's page visits meet the Good threshold for each Core Web Vital. Run regular audits and benchmark results so you can measure the impact of every optimization. Strong Core Web Vitals scores not only improve search rankings — they directly translate to better engagement, lower bounce rates, and higher conversions. 🎯 You now understand what LCP, INP, and CLS measure, how Google scores them, and the specific fixes that improve each — open Site Audit or PageSpeed in Search Atlas to run your first audit and start moving pages into the Good range.