# Peasy SEO — Full Catalog > SEO tools made easy. Peasy SEO provides free browser-based tools at https://peasyseo.com/. All processing happens client-side — files never leave your device. ## Tools (15) ### SERP Preview Preview how your page appears in Google search results See exactly how your page will look in Google search results. Enter a title, description, and URL to preview the snippet with accurate character truncation and pixel-width rendering. - URL: https://peasyseo.com/seo/serp-preview/ - Category: SEO Tools - Processing: client - Steps: 1. Enter your page title (recommended: 50-60 characters) 2. Enter your meta description (recommended: 150-155 characters) 3. Enter your page URL 4. See the live preview update in real time ### OG Tag Debugger Parse and validate Open Graph meta tags from HTML Paste your HTML and instantly see all Open Graph and Twitter Card meta tags extracted and validated. Check for missing required tags and preview how your page will appear when shared on social media. - URL: https://peasyseo.com/seo/og-tag-debugger/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your HTML source code into the input area 2. Click Analyze to extract all OG and Twitter Card tags 3. Review the tag list for missing or invalid tags ### Heading Analyzer Extract and analyze HTML heading structure for SEO Paste your HTML and see the complete heading hierarchy (H1-H6). Identify missing headings, skipped levels, duplicate H1 tags, and other structural issues that affect SEO and accessibility. - URL: https://peasyseo.com/seo/heading-analyzer/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your HTML content into the input area 2. Click Analyze to extract all headings 3. Review the heading tree and any warnings ### Keyword Density Analyzer Analyze keyword frequency and distribution in your content Analyze your content to find the most frequent keywords and phrases. See density percentages for 1-word, 2-word, and 3-word phrases. Identify keyword stuffing risks and optimize your content. - URL: https://peasyseo.com/seo/keyword-density/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your content (plain text or HTML) 2. Set the minimum word length to filter short words 3. Review the keyword frequency table for each n-gram type ### Readability Score Calculate readability scores using five proven formulas Analyze your content's readability using Flesch-Kincaid, Gunning Fog, SMOG Index, Automated Readability Index, and Coleman-Liau Index. Get an overall grade level and actionable suggestions for improvement. - URL: https://peasyseo.com/seo/readability-score/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your content into the input area 2. Click Analyze to calculate all five readability scores 3. Review the average grade level and individual formula results ### XML Sitemap Generator Generate valid XML sitemaps from a list of URLs Enter your URLs (one per line) to generate a standards-compliant XML sitemap. Customize change frequency, priority, and last modified date. Copy or download the result for your website. - URL: https://peasyseo.com/seo/sitemap-generator/ - Category: SEO Tools - Processing: client - Steps: 1. Enter URLs one per line (must start with http:// or https://) 2. Choose a change frequency (daily, weekly, monthly, etc.) 3. Set the priority (0.0 to 1.0) 4. Copy or download the generated XML sitemap ### Schema.org Generator Generate JSON-LD structured data for rich search results Generate valid Schema.org JSON-LD markup for your web pages. Choose from common types like Article, Product, FAQ, Recipe, LocalBusiness, Event, HowTo, and BreadcrumbList. - URL: https://peasyseo.com/seo/schema-generator/ - Category: SEO Tools - Processing: client - Steps: 1. Select a Schema.org type (Article, Product, FAQ, etc.) 2. Fill in the required fields (name, description, URL) 3. Click Generate to create the JSON-LD markup 4. Copy and paste into your page's <head> section ### Link Extractor Extract and categorize all links from HTML content Paste HTML and extract all links with their anchor text, href, and attributes. Categorize links as internal, external, nofollow, or broken. Export the link list for analysis. - URL: https://peasyseo.com/seo/link-extractor/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your HTML content into the input area 2. Click Extract to find all links 3. Review the categorized link list (internal, external, nofollow) ### Canonical Tag Checker Find and validate canonical URL tags in HTML Paste your HTML to find the canonical URL tag and validate it. Check for common issues like missing canonical tags, relative URLs, and mismatched protocols. - URL: https://peasyseo.com/seo/canonical-checker/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your HTML source code 2. Click Check to find canonical tags 3. Review any warnings or issues found ### Robots.txt Analyzer Parse and test robots.txt rules against URLs Paste your robots.txt content and test whether specific URLs are allowed or blocked for different user agents. Identify syntax errors and common configuration mistakes. - URL: https://peasyseo.com/seo/robots-txt-analyzer/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your robots.txt content into the input area 2. Enter a URL to test in the options panel 3. Click Analyze to see parsed rules and test results ### Structured Data Validator Validate JSON-LD structured data syntax and Schema.org types Paste JSON-LD markup or HTML containing structured data to validate syntax, check required properties, and verify Schema.org type usage. Find errors before submitting to Google's Rich Results Test. - URL: https://peasyseo.com/seo/structured-data-validator/ - Category: SEO Tools - Processing: client - Steps: 1. Paste JSON-LD markup or HTML containing structured data 2. Click Validate to check syntax and Schema.org compliance 3. Review errors, warnings, and extracted schema information ### Word Count & SEO Grade Analyze content length with SEO-optimized word count metrics Count words, sentences, and paragraphs in your content. Get an SEO content grade based on word count, reading time estimate, and see how your content length compares to recommended ranges for different content types. - URL: https://peasyseo.com/seo/word-count-seo/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your content (plain text or HTML) 2. View word count, character count, and reading time instantly 3. Check the SEO Content Grade for optimization suggestions 4. Compare your word count against target ranges for your content type ### Meta Length Checker Check meta title & description lengths against Google's display limits Validate your meta title and description against Google's character and pixel-width limits. Get pass/fail status with optimization tips. - URL: https://peasyseo.com/seo/seo-meta-length-checker/ - Category: SEO Tools - Processing: client - Steps: 1. Enter your meta title in the main text area 2. Enter your meta description in the secondary text area 3. Review character counts and pixel-width estimates 4. Fix any warnings or failures shown in the results ### URL Slug Generator Generate SEO-friendly URL slugs from page titles Convert page titles to clean, SEO-optimized URL slugs. Removes stop words, special characters, and formats for maximum search engine friendliness. - URL: https://peasyseo.com/seo/seo-url-slug-generator/ - Category: SEO Tools - Processing: client - Steps: 1. Enter a page title or existing URL slug 2. Choose a mode: generate, analyze, or bulk 3. Review the optimized slug and any recommendations 4. Copy the result and use it in your CMS ### Keyword Density Analyzer Analyze keyword frequency and density across your content Calculate keyword density for single words and multi-word phrases (n-grams). Detect keyword stuffing risks and optimize your on-page SEO. - URL: https://peasyseo.com/seo/seo-keyword-density-analyzer/ - Category: SEO Tools - Processing: client - Steps: 1. Paste your page content into the text area 2. Set the maximum n-gram size (1-4 words) 3. Review the frequency tables for each n-gram level 4. Check for keyword stuffing warnings (>3% density) ## Guides (50) ### Meta Tags for SEO: Title, Description, and Open Graph Meta tags control how your pages appear in search results and social media shares. This guide covers the essential meta tags for SEO, Open Graph for social sharing, and Twitter Card markup. - URL: https://peasyseo.com/guides/meta-tags-seo-guide/ - Category: How-To - Reading time: 1 min - Words: 243 Key takeaways: - Meta tags live in the `<head>` of your HTML and provide information about your page to search engines and social platforms. - The title tag is the single most important on-page SEO element. - The meta description doesn't directly affect rankings but influences click-through rates. - Open Graph controls how your pages appear when shared on Facebook, LinkedIn, and other social platforms: - Twitter uses its own meta tags (`twitter:card`, `twitter:title`, etc.) but falls back to Open Graph tags when Twitter-specific tags are absent. ## Essential Meta Tags Meta tags live in the `<head>` of your HTML and provide information about your page to search engines and social platforms. ## Title Tag The title tag is the single most important on-page SEO element. It appears in search results, browser tabs, and social shares. **Best practices:** - Keep under 60 characters to avoid truncation. - Place your primary keyword near the beginning. - Include your brand name at the end. - Make each page's title unique. ## Meta Description The meta description doesn't directly affect rankings but influences click-through rates. It's your 155-character pitch to searchers. **Best practices:** - Accurately summarize the page content. - Include a call to action. - Include your target keyword (Google bolds matching terms). - Unique per page. ## Open Graph Tags Open Graph controls how your pages appear when shared on Facebook, LinkedIn, and other social platforms: - `og:title` — Title shown in social cards. - `og:description` — Description shown in social cards. - `og:image` — Image displayed (recommended: 1200x630px). - `og:url` — Canonical URL of the page. - `og:type` — Content type (website, article, product). ## Twitter Cards Twitter uses its own meta tags (`twitter:card`, `twitter:title`, etc.) but falls back to Open Graph tags when Twitter-specific tags are absent. ## Common Mistakes - Duplicate titles across many pages. - Missing og:image (social shares show no preview). - Title tag too long (truncated with ...). - Meta description too short or generic. ### How to Optimize Images for SEO Optimize images for search engine visibility and faster page loads. Learn about alt text, file naming, compression, responsive images, lazy loading, and structured data for image SEO. - URL: https://peasyseo.com/guides/how-to-optimize-images-for-seo/ - Category: How-To - Reading time: 1 min - Words: 192 ## Image SEO Fundamentals Images appear in Google Image Search, generate traffic, and affect page ranking through Core Web Vitals. Properly optimized images load fast, are discoverable by search engines, and provide context to crawlers. ## Key Optimization Factors ### File Names Use descriptive, keyword-rich file names separated by hyphens: `blue-mountain-sunrise.jpg` instead of `IMG_4532.jpg`. Search engines use file names as ranking signals. ### Alt Text Write descriptive alt attributes that explain the image content. Alt text serves screen readers and helps search engines understand the image. Keep it under 125 characters. ### File Size & Format Use WebP or AVIF for the best compression-to-quality ratio. Aim for images under 200KB for standard content images and under 100KB for thumbnails. ### Responsive Images Use `srcset` and `sizes` attributes to serve appropriately sized images for each device width. This prevents mobile devices from downloading desktop-sized images. ## Quick Checklist 1. Descriptive file name with target keywords 2. Alt text describing image content (not stuffed with keywords) 3. Compressed to under 200KB using WebP or optimized JPEG 4. Correct dimensions (do not rely on CSS to resize) 5. Lazy loading with `loading="lazy"` for below-fold images ### Meta Tags Optimization: A Complete Guide for 2025-2026 Meta tags are the first impression your page makes on search engines and social platforms. Optimizing title tags, descriptions, and other meta elements directly impacts click-through rates from SERPs. - URL: https://peasyseo.com/guides/meta-tags-optimization-complete-guide/ - Category: How-To - Reading time: 1 min - Words: 276 Key takeaways: - The `<title>` element is the single most impactful on-page SEO factor. - Control how your pages appear when shared on Facebook, LinkedIn, and other platforms: - Twitter uses its own meta tags alongside Open Graph fallbacks: - Duplicate titles across multiple pages - ## The Most Important Meta Tags ### Title Tag The `<title>` element is the single most impactful on-page SEO factor. ## The Most Important Meta Tags ### Title Tag The `<title>` element is the single most impactful on-page SEO factor. It appears in browser tabs, search results, and social shares. | Rule | Guideline | |------|----------| | Length | 50-60 characters (Google truncates at ~580px) | | Primary keyword | Place near the beginning | | Brand name | Append with a separator (" — Brand") | | Uniqueness | Every page must have a distinct title | ### Meta Description Not a ranking factor, but heavily influences click-through rate. Write a compelling 150-160 character summary that includes the target keyword and a clear value proposition. Google rewrites descriptions about 62% of the time, but a well-written description increases the chance it is used as-is. ### Robots Meta Tag `<meta name="robots" content="index, follow">` is the default. Use `noindex` for pages you want crawled but not indexed (admin pages, thank-you pages, duplicate filtered views). ## Open Graph Tags Control how your pages appear when shared on Facebook, LinkedIn, and other platforms: - `og:title` — Share title (can differ from SEO title) - `og:description` — Share description - `og:image` — Preview image (minimum 1200×630px) - `og:type` — Content type (website, article) ## Twitter Card Tags Twitter uses its own meta tags alongside Open Graph fallbacks: - `twitter:card` — Card type (summary, summary_large_image) - `twitter:title` — Falls back to og:title - `twitter:description` — Falls back to og:description ## Common Mistakes - Duplicate titles across multiple pages - Missing or too-short meta descriptions - Using the same OG image for every page - Forgetting the viewport meta tag for mobile - Blocking CSS/JS with robots meta while expecting proper rendering ### Structured Data Implementation: Schema.org for SEO Structured data helps search engines understand your content semantically, enabling rich results like stars, prices, FAQs, and recipe cards in search. This guide covers JSON-LD implementation. - URL: https://peasyseo.com/guides/structured-data-schema-org-guide/ - Category: How-To - Reading time: 1 min - Words: 272 Key takeaways: - Structured data uses a standardized vocabulary (Schema.org) to annotate page content so search engines can parse meaning beyond raw text. - When a page needs multiple schema types (Article plus BreadcrumbList plus Organization), wrap them in a single `@graph` array rather than multiple separate script tags. - Missing required fields (e.g., `image` for Article) ## What Is Structured Data Structured data uses a standardized vocabulary (Schema.org) to annotate page content so search engines can parse meaning beyond raw text. The preferred format is JSON-LD (JavaScript Object Notation for Linked Data), embedded in a `<script type="application/ld+json">` tag. ## Rich Result Types | Schema Type | Rich Result | Use Case | |-------------|------------|----------| | Article | News carousel | Blog posts, news | | Product | Price, rating, availability | E-commerce | | FAQPage | Expandable Q&A | FAQ sections | | HowTo | Step-by-step cards | Tutorials | | Recipe | Image, time, rating | Food content | | BreadcrumbList | Navigation trail | All pages | | WebApplication | App info | Online tools | | Organization | Knowledge panel | About pages | ## JSON-LD Best Practices ### Use @graph for Multiple Types When a page needs multiple schema types (Article plus BreadcrumbList plus Organization), wrap them in a single `@graph` array rather than multiple separate script tags. ### Match Visible Content Google requires that structured data reflects content actually visible on the page. Marking up content that users cannot see violates guidelines and can result in manual actions. ### Test Before Deploying Use Google's Rich Results Test and Schema Markup Validator to verify your JSON-LD is error-free before pushing to production. ## Common Errors - Missing required fields (e.g., `image` for Article) - Using incorrect types (e.g., WebPage instead of Article for blog posts) - Hardcoded URLs instead of dynamic values - Forgetting to escape special characters in JSON strings - Nesting types incorrectly (publisher inside Article should be an Organization, not a string) ### Internal Linking Optimization for Better SEO Rankings Internal links distribute PageRank, establish content hierarchy, and help search engines discover pages. A strategic internal linking structure can significantly improve rankings without creating new content. - URL: https://peasyseo.com/guides/internal-linking-optimization/ - Category: Best Practice - Reading time: 1 min - Words: 270 Key takeaways: - Internal links serve three purposes: they help users navigate, they help search engines discover and index pages, and they pass link equity (PageRank) from authoritative pages to ones that need ranking support. - Organize content into topic clusters with a pillar page at the center. - Every important page should be reachable within three clicks from the homepage. - Links within body content carry more weight than navigation or footer links. - Use a crawler (Screaming Frog, Sitebulb) to map your internal link graph. ## Why Internal Linking Matters Internal links serve three purposes: they help users navigate, they help search engines discover and index pages, and they pass link equity (PageRank) from authoritative pages to ones that need ranking support. ## Content Hub Model Organize content into topic clusters with a pillar page at the center. The pillar page covers a broad topic, and cluster pages dive into subtopics. Each cluster page links to the pillar and vice versa. ## Anchor Text Rules | Do | Don't | |-----|-------| | Use descriptive, keyword-rich anchors | Use 'click here' or 'read more' | | Vary anchor text naturally | Repeat exact-match anchors excessively | | Link contextually within paragraphs | Stuff links into footers or sidebars only | ## Link Depth Every important page should be reachable within three clicks from the homepage. Pages buried five or more clicks deep receive significantly less crawl attention and link equity. ## Practical Tactics ### Contextual Links Links within body content carry more weight than navigation or footer links. When writing a new article, identify 3-5 existing pages that are topically related and link to them naturally. ### Related Content Sections Add a 'Related Tools' or 'See Also' section at the bottom of each page. This creates a secondary linking layer beyond the main navigation. ### Breadcrumb Navigation Breadcrumbs provide hierarchical links and generate BreadcrumbList structured data. They improve both UX and SEO crawlability. ## Auditing Internal Links Use a crawler (Screaming Frog, Sitebulb) to map your internal link graph. Look for orphan pages (no internal links pointing to them), excessive link depth, and broken internal links. ### Hreflang Implementation for Multilingual SEO Hreflang tags tell search engines which language and regional version of a page to show users. Incorrect implementation can cause the wrong language to appear in search results. - URL: https://peasyseo.com/guides/hreflang-implementation-multilingual-seo/ - Category: Troubleshooting - Reading time: 1 min - Words: 240 Key takeaways: - When a page exists in multiple languages, hreflang annotations help Google serve the correct version to users based on their language and location. - <link rel="alternate" hreflang="en" href="https://example.com/page/"> - Missing self-referencing hreflang tags - Use Ahrefs' hreflang audit or Merkle's hreflang tag testing tool. ## What Hreflang Does When a page exists in multiple languages, hreflang annotations help Google serve the correct version to users based on their language and location. Without hreflang, Google may choose the wrong version or flag pages as duplicates. ## Implementation Methods ### HTML Link Tags (Recommended) ```html <link rel="alternate" hreflang="en" href="https://example.com/page/"> <link rel="alternate" hreflang="ko" href="https://example.com/ko/page/"> <link rel="alternate" hreflang="ja" href="https://example.com/ja/page/"> <link rel="alternate" hreflang="x-default" href="https://example.com/page/"> ``` ### HTTP Headers For non-HTML files (PDFs): `Link: <url>; rel="alternate"; hreflang="en"` ### XML Sitemap ```xml <url> <loc>https://example.com/page/</loc> <xhtml:link rel="alternate" hreflang="en" href="..."/> <xhtml:link rel="alternate" hreflang="ko" href="..."/> </url> ``` ## Critical Rules | Rule | Consequence of Violation | |------|------------------------| | Every page must reference ALL language versions including itself | Incomplete annotations are ignored entirely | | Annotations must be reciprocal (A→B AND B→A) | One-way annotations are ignored | | Use ISO 639-1 language codes | Invalid codes break all hreflang | | Include x-default for fallback | Users in unsupported regions see wrong page | | Canonical and hreflang must agree | Conflicting signals confuse Google | ## Common Mistakes - Missing self-referencing hreflang tags - Using `zh` instead of `zh-Hans` or `zh-Hant` - Non-reciprocal annotations (English page links to Korean but Korean does not link back) - hreflang pointing to redirected or noindexed URLs - Mixing HTML and sitemap methods (choose one) ## Validation Use Ahrefs' hreflang audit or Merkle's hreflang tag testing tool. Check Search Console's International Targeting report for errors. ### Structured Data and Schema.org: A Practical Guide Structured data helps search engines understand your content and can generate rich results like star ratings, FAQs, and product cards. Learn how to implement Schema.org markup effectively with JSON-LD. - URL: https://peasyseo.com/guides/structured-data-schema-org/ - Category: How-To - Reading time: 1 min - Words: 225 Key takeaways: - Structured data uses a standardized vocabulary (Schema.org) to describe your content to search engines. - Google recommends JSON-LD (JavaScript Object Notation for Linked Data) over microdata or RDFa. - Mark up visible content only — don't include hidden data. - ## Best Practices - Mark up visible content only — don't include hidden data. ## What Is Structured Data? Structured data uses a standardized vocabulary (Schema.org) to describe your content to search engines. It enables rich results — enhanced search listings with images, ratings, prices, and other visual elements. ## JSON-LD: The Recommended Format Google recommends JSON-LD (JavaScript Object Notation for Linked Data) over microdata or RDFa. JSON-LD sits in a `<script>` tag and doesn't mix with your HTML markup. ## Common Schema Types | Schema Type | Rich Result | Best For | |------------|-------------|----------| | Article | Article byline, date | Blog posts, news | | FAQPage | Expandable Q&A | FAQ sections | | HowTo | Step-by-step | Tutorials | | Product | Price, availability, reviews | E-commerce | | WebApplication | App info | Online tools | | BreadcrumbList | Breadcrumb trail | Navigation | ## Implementation Steps 1. Identify the primary content type of each page. 2. Add the appropriate JSON-LD script to the `<head>` or `<body>`. 3. Include all required properties for the schema type. 4. Test with Google's Rich Results Test tool. 5. Monitor in Google Search Console under Enhancements. ## Best Practices - Mark up visible content only — don't include hidden data. - Use the most specific schema type available. - Include BreadcrumbList on every page. - Test after every change. - Don't mark up content that isn't on the page. ### How to Strip EXIF Metadata From Photos for Privacy Photos contain hidden metadata including GPS coordinates, device info, and timestamps. Before sharing photos online, learn how to remove this data to protect your privacy and prevent location tracking. - URL: https://peasyseo.com/guides/strip-exif-metadata-privacy/ - Category: How-To - Reading time: 1 min - Words: 234 Key takeaways: - EXIF (Exchangeable Image File Format) metadata is automatically embedded in photos by cameras and smartphones. - Browser-based EXIF strippers process your photos locally without uploading them. - Disable GPS tagging in your phone's camera settings. - Your images never leave your device, which is the safest approach. ## What Is EXIF Data? EXIF (Exchangeable Image File Format) metadata is automatically embedded in photos by cameras and smartphones. This data includes technical shooting parameters and often sensitive personal information. ## Types of Hidden Data | Data Type | Privacy Risk | Example | |-----------|-------------|--------| | GPS coordinates | High | Home address, workplace | | Date/time | Medium | Travel patterns, daily routine | | Device model | Low | Phone model, camera type | | Serial number | Medium | Unique device identifier | | Thumbnail | Medium | Pre-edit version of cropped photo | | Software | Low | Editing tools used | ## How to Remove EXIF Data ### Client-Side Tools Browser-based EXIF strippers process your photos locally without uploading them. Your images never leave your device, which is the safest approach. ### Selective Removal Sometimes you want to keep some metadata (like the date for organization) while removing sensitive fields (like GPS). Selective removal lets you choose which fields to strip. ### Before Sharing Online Some social media platforms strip EXIF data automatically (Instagram, Twitter), but many don't (forums, email, direct sharing). When in doubt, strip metadata before sharing. ## Prevention - Disable GPS tagging in your phone's camera settings. - Review sharing settings in your photo apps. - Use share sheets that strip metadata by default. - Be especially careful with photos of children or your home. ### Image Optimization for Core Web Vitals and SEO Images directly impact Core Web Vitals scores, especially Largest Contentful Paint. Learn how to optimize images for faster loading, better SEO rankings, and improved user experience across all devices. - URL: https://peasyseo.com/guides/image-optimization-core-web-vitals/ - Category: Best Practice - Reading time: 1 min - Words: 228 Key takeaways: - Google's Core Web Vitals measure real-world user experience. - The LCP element is often a hero image or the largest visible image on the page. - Layout shifts caused by images happen when the browser doesn't know the image dimensions before it loads: - Write descriptive alt text that accurately describes the image content. - ## SEO Image Best Practices ### Alt Text Write descriptive alt text that accurately describes the image content. ## Images and Core Web Vitals Google's Core Web Vitals measure real-world user experience. Images affect two key metrics: Largest Contentful Paint (LCP), which measures loading speed, and Cumulative Layout Shift (CLS), which measures visual stability. ## Optimizing for LCP The LCP element is often a hero image or the largest visible image on the page. To improve LCP: - **Serve correctly sized images**: Don't serve a 2400px image in a 600px container. - **Use modern formats**: WebP is 25-35% smaller than JPEG at equivalent quality. - **Implement lazy loading**: Use `loading="lazy"` for below-the-fold images, but never on the LCP image itself. - **Preload the LCP image**: Use `<link rel="preload">` to start loading early. ## Preventing CLS Layout shifts caused by images happen when the browser doesn't know the image dimensions before it loads: - Always include `width` and `height` attributes on `<img>` tags. - Use CSS `aspect-ratio` for responsive images. - Avoid replacing placeholder images with differently-sized final images. ## SEO Image Best Practices ### Alt Text Write descriptive alt text that accurately describes the image content. Good alt text helps search engines understand image context and improves accessibility. ### File Names Use descriptive, hyphenated file names instead of generic ones. `blue-cotton-t-shirt.webp` is far better than `IMG_20240315_001.jpg`. ### Image Sitemaps For important images, include them in your XML sitemap to ensure search engines discover and index them. ### SEO Audit Tools Compared: Lighthouse, PageSpeed, and GSC Multiple SEO tools are available, each measuring different aspects of your site. This comparison helps you understand what each tool measures and when to use which tool for auditing your site's SEO health. - URL: https://peasyseo.com/guides/seo-audit-tools-compared/ - Category: Comparison - Reading time: 1 min - Words: 266 Key takeaways: - No single tool covers all aspects of SEO. - Lighthouse is an open-source tool built into Chrome DevTools. - PSI combines Lighthouse lab data with Chrome User Experience Report (CrUX) field data from real users over the past 28 days. - GSC shows how Google actually crawls and indexes your site. - It runs automated audits for performance, accessibility, best practices, and SEO. ## The SEO Tool Ecosystem No single tool covers all aspects of SEO. Understanding what each tool measures helps you build a comprehensive audit workflow. ## Google Lighthouse Lighthouse is an open-source tool built into Chrome DevTools. It runs automated audits for performance, accessibility, best practices, and SEO. **Strengths:** Free, detailed recommendations, reproducible, CI/CD integration. **Limitations:** Lab data only (simulated), single-page analysis, no historical data. ## Google PageSpeed Insights PSI combines Lighthouse lab data with Chrome User Experience Report (CrUX) field data from real users over the past 28 days. **Strengths:** Real user data, Core Web Vitals pass/fail, free. **Limitations:** Origin-level field data may mask page-level issues. ## Google Search Console GSC shows how Google actually crawls and indexes your site. It reports indexing status, search queries, click-through rates, and structured data errors. **Strengths:** Real crawl and index data, search performance metrics, free. **Limitations:** Data delay (2-3 days), no competitor analysis. ## Comparison | Aspect | Lighthouse | PageSpeed Insights | Search Console | |--------|-----------|-------------------|----------------| | Data type | Lab | Lab + Field | Real crawl data | | CWV metrics | Simulated | Real user + simulated | Real user | | SEO audit | Basic | Basic | Comprehensive | | Indexing status | No | No | Yes | | Search queries | No | No | Yes | | Competitor data | No | No | No | ## Recommended Workflow 1. **Weekly**: Check Search Console for new errors and indexing issues. 2. **Monthly**: Run Lighthouse audits on key pages. 3. **After changes**: Use PageSpeed Insights to verify CWV aren't impacted. ### Container Formats Explained: MP4, MKV, WebM, and MOV Container formats wrap video, audio, and metadata into a single file. Understanding the difference between MP4, MKV, WebM, and MOV helps you choose the right wrapper for your video content. - URL: https://peasyseo.com/guides/video-container-formats-explained/ - Category: Comparison - Reading time: 1 min - Words: 243 Key takeaways: - A common source of confusion is the difference between codecs and containers. - MP4 is the most widely supported container format. - Matroska (MKV) supports virtually every codec and feature: multiple audio tracks, subtitle tracks, chapters, attachments, and metadata. - WebM is Google's container for VP8, VP9, and AV1 codecs. - QuickTime MOV is Apple's container format. ## Codec vs Container A common source of confusion is the difference between codecs and containers. The codec determines how video is compressed; the container determines how the compressed data is packaged. Think of it like a shipping box (container) holding various items (codec streams, subtitles, metadata). The same item can go in different boxes. ## MP4 (.mp4): Universal Container MP4 is the most widely supported container format. It supports H.264, H.265, AAC, and many other codecs. It's the default for web video, social media, and mobile devices. **Supports:** H.264, H.265, AAC, subtitles (limited). ## MKV (.mkv): The Kitchen Sink Matroska (MKV) supports virtually every codec and feature: multiple audio tracks, subtitle tracks, chapters, attachments, and metadata. It's popular for media libraries. **Supports:** Everything — H.264, H.265, AV1, VP9, FLAC, DTS, chapters. ## WebM (.webm): Web-Optimized WebM is Google's container for VP8, VP9, and AV1 codecs. It's designed for web delivery and is supported natively in all modern browsers. **Supports:** VP8, VP9, AV1, Vorbis, Opus. ## MOV (.mov): Apple's Container QuickTime MOV is Apple's container format. It's functionally similar to MP4 but has better support for ProRes and Apple-specific codecs. **Supports:** H.264, H.265, ProRes, AAC, PCM. ## Choosing the Right Container | Use Case | Recommended Container | |----------|----------------------| | Web delivery | MP4 or WebM | | Media archive | MKV | | Apple ecosystem | MOV | | Social media upload | MP4 | | Professional editing | MOV (ProRes) | ### How to Write Effective Title Tags and Meta Descriptions Title tags and meta descriptions are the first thing users see in search results. Learn character limits, keyword placement, and click-through rate optimization. - URL: https://peasyseo.com/guides/how-to-write-title-tags-meta-descriptions/ - Category: How-To - Reading time: 1 min - Words: 174 Key takeaways: - Title tags should be 50-60 characters to avoid truncation in search results. - Meta descriptions should be 150-160 characters. - Emotional triggers increase CTR. - Duplicate titles**: Every page needs a unique title. - Use SERP preview tools to see how your title and description appear in Google results. ## Title Tag Best Practices Title tags should be 50-60 characters to avoid truncation in search results. Place the primary keyword near the beginning. Include your brand name, separated by a pipe or dash. Make each page's title unique. ## Meta Description Guidelines Meta descriptions should be 150-160 characters. They don't directly affect rankings but significantly influence click-through rates. Include a clear value proposition and a call-to-action. ## Click-Through Rate Optimization Emotional triggers increase CTR. Use power words like 'Complete,' 'Ultimate,' 'Step-by-Step,' and numbers ('7 Ways to...'). Questions in titles ('How Much Does X Cost?') match search intent directly. ## Common Mistakes - **Duplicate titles**: Every page needs a unique title. - **Keyword stuffing**: 'Shoes | Buy Shoes | Cheap Shoes | Best Shoes' looks spammy. - **Missing brand**: Include brand name for recognition and trust. - **Generic descriptions**: 'Welcome to our website' tells users nothing. ## Testing Titles Use SERP preview tools to see how your title and description appear in Google results. Test on both desktop (wider display) and mobile (narrower truncation). ### How to Convert HEIC to JPG Without Quality Loss Convert Apple's HEIC/HEIF photos to universally compatible JPEG format while preserving image quality and metadata. - URL: https://peasyseo.com/guides/how-to-convert-heic-to-jpg-without-quality-loss/ - Category: How-To - Reading time: 1 min - Words: 291 ## Converting HEIC to JPG HEIC (High Efficiency Image Container) is Apple's default photo format since iOS 11. While it offers 50% better compression than JPEG, many platforms and applications still don't support it. Converting to JPG ensures universal compatibility. ### Why HEIC Exists HEIC uses the HEVC (H.265) codec for image compression, achieving significantly smaller file sizes at equivalent quality. A 12-megapixel iPhone photo might be 2.5MB as HEIC versus 5MB as JPEG. HEIC also supports features JPEG lacks: 16-bit color depth, transparency, image sequences, and non-destructive edits stored as metadata. ### Quality Preservation When converting HEIC to JPG, you're re-encoding from one lossy format to another, which introduces generation loss. Minimize this by using quality setting 92-95 (out of 100) — higher values have diminishing returns while dramatically increasing file size. For archival purposes, convert to PNG (lossless) instead of JPG. ### Metadata Handling HEIC files contain EXIF metadata including GPS location, camera settings, and creation date. Ensure your converter preserves this metadata during conversion — some tools strip it by default. If privacy is a concern, deliberately remove GPS data during conversion while preserving camera information. ### Batch Conversion For converting entire photo libraries, browser-based tools process files locally without uploading. Select all HEIC files, choose JPG output with quality 93, and download the converted batch. Processing happens entirely in your browser using WebAssembly — no server upload required, keeping your photos private. ### When to Keep HEIC If you're only sharing photos with other Apple users, or storing them in iCloud, keep the HEIC format — you'll save significant storage space with no compatibility issues. Convert to JPG only when sharing with non-Apple users, uploading to platforms that don't support HEIC, or embedding in documents and presentations. ### How to Implement Hreflang Tags for International SEO Hreflang tags tell search engines which language and regional version of a page to show users. Learn proper implementation to avoid duplicate content issues. - URL: https://peasyseo.com/guides/how-to-implement-hreflang-tags/ - Category: How-To - Reading time: 1 min - Words: 186 Key takeaways: - Hreflang signals to search engines that multiple versions of a page exist in different languages or for different regions. - <link rel="alternate" hreflang="en" href="https://example.com/page" /> - Every page must include a hreflang tag pointing to itself. - Hreflang tags must be reciprocal. - The `x-default` hreflang indicates the default or fallback page for users whose language/region doesn't match any specific version. ## What Hreflang Does Hreflang signals to search engines that multiple versions of a page exist in different languages or for different regions. Without hreflang, Google might show the English page to French users, or treat translations as duplicate content. ## Syntax ```html <link rel="alternate" hreflang="en" href="https://example.com/page" /> <link rel="alternate" hreflang="fr" href="https://example.com/fr/page" /> <link rel="alternate" hreflang="x-default" href="https://example.com/page" /> ``` ## Self-Referencing Required Every page must include a hreflang tag pointing to itself. If the French page links to the English version, it must also link to itself as the French version. ## Return Tags Required Hreflang tags must be reciprocal. If Page A references Page B, Page B must reference Page A. Missing return tags cause Google to ignore the hreflang. ## x-default The `x-default` hreflang indicates the default or fallback page for users whose language/region doesn't match any specific version. Typically points to the English version or a language-selection page. ## Implementation Methods Hreflang can be implemented via HTML `<link>` tags, HTTP headers (for non-HTML resources), or XML sitemaps. Sitemaps are recommended for sites with many languages because they don't add markup to every page. ### Google Search Console vs Ahrefs vs SEMrush SEO tools vary widely in features, data sources, and pricing. Compare the leading options to find the right tool for your needs and budget. - URL: https://peasyseo.com/guides/google-search-console-vs-ahrefs-vs-semrush/ - Category: Comparison - Reading time: 1 min - Words: 199 Key takeaways: - GSC provides authoritative data directly from Google — actual search queries, impressions, click-through rates, and indexing status. - Ahrefs has the largest backlink database and is the go-to tool for link analysis. - SEMrush offers the broadest feature set — SEO, PPC, social media, and content marketing tools. - Start with Google Search Console (free, authoritative data). ## Google Search Console: Free Official Data GSC provides authoritative data directly from Google — actual search queries, impressions, click-through rates, and indexing status. It's free but limited to your own site and the last 16 months of data. ## Ahrefs: Backlink Powerhouse Ahrefs has the largest backlink database and is the go-to tool for link analysis. Its Site Explorer shows competitor backlinks, organic keywords, and traffic estimates. Strong content explorer for finding link-worthy topics. ## SEMrush: All-in-One Suite SEMrush offers the broadest feature set — SEO, PPC, social media, and content marketing tools. Its keyword research includes search intent classification and SERP feature analysis. Strong competitor intelligence. ## Comparison | Feature | GSC | Ahrefs | SEMrush | |---------|-----|--------|--------| | Price | Free | $99+/mo | $130+/mo | | Data source | Google (official) | Crawler | Crawler + clickstream | | Backlink analysis | Basic | Best | Good | | Keyword research | Limited | Good | Best | | Competitor analysis | None | Good | Best | ## Recommendation Start with Google Search Console (free, authoritative data). Add Ahrefs when you need competitor backlink analysis. Consider SEMrush if you need an all-in-one marketing platform. ### WAV vs FLAC vs ALAC: Lossless Audio Format Comparison Lossless audio preserves full quality but formats differ in compression, metadata support, and compatibility. Compare WAV, FLAC, and ALAC. - URL: https://peasyseo.com/guides/wav-vs-flac-vs-alac-comparison/ - Category: Comparison - Reading time: 1 min - Words: 207 Key takeaways: - WAV stores raw PCM audio data with minimal compression. - FLAC compresses audio by 50-60% compared to WAV with zero quality loss. - ALAC provides similar compression to FLAC but is Apple's proprietary format. - Use FLAC for archival and non-Apple playback. ## WAV: Uncompressed Standard WAV stores raw PCM audio data with minimal compression. File sizes are large (about 10 MB per minute for CD quality) but decoding is instant because there's nothing to decompress. WAV is universally supported. ## FLAC: Free Lossless Audio Codec FLAC compresses audio by 50-60% compared to WAV with zero quality loss. The original waveform is perfectly reconstructed on playback. FLAC supports metadata, album art, and up to 8 channels. ## ALAC: Apple Lossless ALAC provides similar compression to FLAC but is Apple's proprietary format. It's natively supported in iTunes, Apple Music, and iOS devices. ALAC is now open-source but sees less adoption outside the Apple ecosystem. ## Comparison | Feature | WAV | FLAC | ALAC | |---------|-----|------|------| | Compression | None | ~50-60% | ~50-60% | | Quality | Lossless | Lossless | Lossless | | Metadata | Basic | Excellent | Good | | Apple support | Yes | No (natively) | Yes | | Android support | Yes | Yes | Limited | | Streaming | No | Yes | Yes | ## Recommendation Use FLAC for archival and non-Apple playback. Use ALAC for Apple-centric workflows. Use WAV for audio editing (universal DAW compatibility) and as a master format. ### Page Speed Optimization Best Practices for SEO Page speed is a confirmed Google ranking factor. Learn how to optimize Core Web Vitals and page load times for better search performance. - URL: https://peasyseo.com/guides/page-speed-optimization-seo/ - Category: Best Practice - Reading time: 1 min - Words: 166 Key takeaways: - Google's ranking signal uses three metrics: LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). - Images are typically the largest page elements. - CSS and synchronous JavaScript block page rendering. - Set appropriate Cache-Control headers. - Custom fonts can block text rendering. ## Core Web Vitals Google's ranking signal uses three metrics: LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). Good scores are LCP < 2.5s, INP < 200ms, and CLS < 0.1. ## Image Optimization Images are typically the largest page elements. Convert to WebP/AVIF, resize to display dimensions, use responsive `srcset`, and lazy-load below-fold images. This alone can improve LCP by 1-3 seconds. ## Render-Blocking Resources CSS and synchronous JavaScript block page rendering. Inline critical CSS in `<head>`, defer non-critical CSS, and add `defer` or `async` to script tags. Move third-party scripts to page bottom. ## Caching Strategy Set appropriate Cache-Control headers. Static assets (CSS, JS, images) can be cached for a year with content-hash filenames. HTML pages should use shorter cache periods or `no-cache` with ETag validation. ## Font Loading Custom fonts can block text rendering. Use `font-display: swap` to show text immediately with fallback fonts. Subset fonts to include only needed characters. Preload critical fonts with `<link rel="preload">`. ### Slug Generation and URL-Safe String Best Practices Generate clean, SEO-friendly URL slugs from titles and names, handling Unicode, transliteration, and edge cases. - URL: https://peasyseo.com/guides/slug-generation-url-safe-strings/ - Category: Best Practice - Reading time: 1 min - Words: 243 ## URL Slug Generation Clean URL slugs improve SEO, readability, and shareability. Converting arbitrary text into URL-safe strings requires handling Unicode characters, multiple whitespace patterns, and special characters consistently. ### Basic Slug Rules A well-formed slug uses only lowercase ASCII letters, digits, and hyphens. Leading and trailing hyphens are removed. Multiple consecutive hyphens are collapsed to one. Common word separators (spaces, underscores, dots) become hyphens. The result should be a readable, meaningful summary of the content. ### Unicode and Transliteration For international content, transliterate Unicode characters to ASCII equivalents before slugifying: ü→ue, ñ→n, 日本→nihon. Libraries like python-slugify and slugify.js handle this automatically for most scripts. For CJK characters without standard transliterations, consider using romanization systems (Pinyin, Romaji) or keeping the original characters in the URL if your stack supports IRI. ### SEO Considerations Keep slugs under 60 characters — search engines may truncate longer URLs. Remove stop words (the, a, an, is, of) to focus on keywords, but only if the result remains readable. Avoid including dates or version numbers unless the content is inherently temporal. Once a slug is published and indexed, never change it without setting up a 301 redirect. ### Collision Handling When two different titles generate the same slug, append a numeric suffix (my-title, my-title-2, my-title-3). Check for collisions at generation time, not just at database insert time, to provide immediate feedback. For high-volume systems, consider appending a short random suffix instead of sequential numbers to avoid race conditions. ### Open Graph and Twitter Card Meta Tags Guide Configure OG and Twitter Card meta tags for rich social media previews when your pages are shared. - URL: https://peasyseo.com/guides/open-graph-twitter-card-meta-tags-guide/ - Category: How-To - Reading time: 1 min - Words: 299 Key takeaways: - When someone shares your URL on social media, the platform scrapes your page for Open Graph and Twitter Card meta tags to generate a preview card. - ### Essential Open Graph Tags `og:title` — the title shown in the preview (may differ from the page title). - The image must be at least 200×200 for Facebook, but larger images get better previews. - ### Common Mistakes Using relative image URLs (must be absolute with protocol). ## Social Media Meta Tags When someone shares your URL on social media, the platform scrapes your page for Open Graph and Twitter Card meta tags to generate a preview card. Without these tags, previews show a generic link or use AI-guessed content — neither of which is ideal. ### Essential Open Graph Tags `og:title` — the title shown in the preview (may differ from the page title). `og:description` — 1-2 sentence summary. `og:image` — the preview image URL (absolute, not relative). `og:url` — the canonical URL. `og:type` — usually "website" or "article". These five tags are the minimum for a proper preview on Facebook, LinkedIn, Discord, Slack, and most platforms. ### Open Graph Image Requirements Facebook recommends 1200×630 pixels. LinkedIn prefers 1200×627. The image must be at least 200×200 for Facebook, but larger images get better previews. Always use HTTPS URLs. File size should be under 5MB. JPEG and PNG are universally supported; WebP support varies by platform. If the image is too small, Facebook may not show it at all. ### Twitter Card Types `twitter:card` = "summary" shows a small square image beside the title. "summary_large_image" shows a large image above the title. "player" embeds video/audio. Large image cards get significantly more engagement. Include `twitter:site` (your @handle) and `twitter:creator` (the author's @handle). ### Debugging Previews Facebook: facebook.com/debug/ (Sharing Debugger). Twitter: cards-dev.twitter.com/validator. LinkedIn: linkedin.com/post-inspector/. These tools show exactly what the platform sees. They also force cache refresh — useful when you've updated tags but the old preview persists. ### Common Mistakes Using relative image URLs (must be absolute with protocol). Missing og:image dimensions (og:image:width, og:image:height help platforms render faster). Not updating meta tags for different pages (every page using the same og:image). Forgetting that platforms aggressively cache previews — use the debug tools to refresh cache after changes. ### Technical SEO Audit Checklist for New Websites Before focusing on content and links, ensure your website's technical foundation is solid. This checklist covers crawlability, indexability, speed, and structured data. - URL: https://peasyseo.com/guides/technical-seo-audit-checklist-new-sites/ - Category: How-To - Reading time: 1 min - Words: 278 Key takeaways: - Search engines must be able to discover and access your pages. - Verify that internal linking creates paths from the homepage to every important page within 3-4 clicks. - ## Crawlability Search engines must be able to discover and access your pages. ## Crawlability Search engines must be able to discover and access your pages. Check robots.txt to ensure important pages aren't blocked. Submit an XML sitemap through Google Search Console. Verify that internal linking creates paths from the homepage to every important page within 3-4 clicks. ### Indexability Not every page should be indexed. Use `noindex` for pagination pages, filtered views, and internal search results. Implement canonical tags to consolidate duplicate or near-duplicate pages. Check for soft 404s (pages that return 200 OK but display "not found" content). Ensure only one version of each URL is accessible (choose www or non-www, http or https, trailing slash or not). ### Site Speed Core Web Vitals are ranking factors. Largest Contentful Paint (LCP) should be under 2.5 seconds. Cumulative Layout Shift (CLS) should be under 0.1. Interaction to Next Paint (INP) should be under 200ms. Compress images, minify CSS/JS, enable HTTP/2, and use a CDN. ### Mobile Usability Google uses mobile-first indexing — your mobile site is the primary version for ranking. Test with Google's Mobile-Friendly Test. Check that text is readable without zooming, buttons are large enough to tap, and content doesn't extend beyond the viewport. ### Structured Data Implement relevant Schema.org markup for your content type. At minimum, add Organization (homepage), BreadcrumbList (all pages), and Article or Product schemas where appropriate. Validate with Google's Rich Results Test. Structured data doesn't directly affect rankings but improves click-through rates through rich snippets. ### HTTPS and Security Serve everything over HTTPS. Mixed content (HTTP resources on HTTPS pages) triggers browser warnings. Set HTTP security headers: Strict-Transport-Security, X-Content-Type-Options, and X-Frame-Options. Register your site in Google Search Console for both HTTP and HTTPS versions. ### Image SEO Best Practices: Alt Text, File Names, and Lazy Loading Optimized images improve search rankings, accessibility, and page speed. Learn how to name, describe, and serve images for maximum SEO benefit. - URL: https://peasyseo.com/guides/image-seo-best-practices/ - Category: Best Practice - Reading time: 1 min - Words: 164 Key takeaways: - Search engines use file names as a ranking signal. - Alt text serves two purposes: accessibility for screen reader users and context for search engines. - Use the `srcset` attribute to serve different sizes for different devices. - Add `loading="lazy"` to images below the fold. - For image-heavy sites, include images in your XML sitemap. ## File Naming Search engines use file names as a ranking signal. Name images descriptively: `blue-running-shoes-nike-pegasus.webp` is far better than `IMG_4392.jpg`. Use hyphens to separate words and keep names under 50 characters. ## Alt Text Alt text serves two purposes: accessibility for screen reader users and context for search engines. Write alt text that describes what the image shows in 1-2 sentences. Avoid keyword stuffing — describe naturally. ## Responsive Images Use the `srcset` attribute to serve different sizes for different devices. A phone doesn't need a 4000px image. Providing appropriate sizes reduces bandwidth and improves Core Web Vitals scores. ## Lazy Loading Add `loading="lazy"` to images below the fold. This defers loading until the image is about to enter the viewport, significantly improving initial page load time. Never lazy-load the LCP (Largest Contentful Paint) image. ## Image Sitemaps For image-heavy sites, include images in your XML sitemap. This helps search engines discover images that might be loaded dynamically or embedded in JavaScript galleries. ### Technical SEO Checklist for New Websites Complete technical SEO setup checklist for new websites covering crawling, indexing, performance, and structured data. - URL: https://peasyseo.com/guides/technical-seo-checklist-new-websites/ - Category: How-To - Reading time: 1 min - Words: 293 ## Technical SEO for New Websites Getting technical SEO right from the start prevents costly fixes later. This checklist covers the foundations that every new website needs before focusing on content and backlinks. ### Crawling and Indexing Create and submit an XML sitemap to Google Search Console and Bing Webmaster Tools. Configure robots.txt to allow crawling of all public pages while blocking admin, staging, and duplicate content paths. Verify robots.txt doesn't accidentally block CSS/JS files that Googlebot needs for rendering. Set up Google Search Console and verify ownership via DNS record. ### URL Structure Use descriptive, keyword-rich URLs: /blog/seo-checklist not /blog/post-123. Enforce consistent URL format: trailing slash or not (pick one), www or non-www (redirect the other). Implement canonical tags on every page to prevent duplicate content issues. Ensure all internal links use the canonical URL format. ### Performance Achieve Core Web Vitals targets: LCP under 2.5 seconds, CLS under 0.1, INP under 200ms. Compress images (WebP format), minify CSS/JS, enable text compression (Brotli/gzip), and implement browser caching. Use lazy loading for below-the-fold images. Consider a CDN for global audiences. ### Mobile Experience Verify mobile-friendliness with Google's Mobile-Friendly Test. Use responsive design (not separate mobile URLs). Ensure tap targets are at least 48×48px with sufficient spacing. Test with real devices, not just browser emulators. Mobile-first indexing means Google evaluates your mobile version, not desktop. ### Structured Data Implement JSON-LD structured data: Organization (homepage), BreadcrumbList (all pages), Article (blog posts), FAQ (FAQ pages), and domain-specific types. Validate with Google's Rich Results Test. Monitor structured data errors in Search Console. ### Security Enforce HTTPS on all pages. Set HSTS headers. Implement security headers (CSP, X-Frame-Options, X-Content-Type-Options). Set up a security.txt file. These are not just security measures — Google uses HTTPS as a ranking signal. ### Schema.org Markup: A Practical Implementation Guide Schema.org structured data helps search engines understand your content and can trigger rich results. Learn which schema types to prioritize and how to implement them correctly. - URL: https://peasyseo.com/guides/schema-org-markup-implementation-guide/ - Category: How-To - Reading time: 1 min - Words: 246 Key takeaways: - Schema.org provides a vocabulary for describing web content in a machine-readable format. - ### Essential Schema Types Organization: Include on your homepage with name, URL, logo, contact information, and social profiles. - ### Common Mistakes Marking up content that isn't visible on the page violates Google's guidelines — structured data must reflect visible content. ## What Schema.org Does Schema.org provides a vocabulary for describing web content in a machine-readable format. Search engines use it to understand the context and relationships of your content, enabling rich results (star ratings, FAQs, recipes, events, etc.) in search results. ### Implementation Formats JSON-LD is the recommended format — it's a script block in the page head, separate from the HTML content. Microdata embeds schema in HTML attributes, making it harder to maintain. RDFa is similar to microdata but more verbose. Google explicitly recommends JSON-LD. ### Essential Schema Types Organization: Include on your homepage with name, URL, logo, contact information, and social profiles. BreadcrumbList: Add to every page to show the navigation hierarchy. WebSite with SearchAction: Enables the sitelinks search box in Google results. Article/BlogPosting: For editorial content, include headline, author, datePublished, and image. ### Common Mistakes Marking up content that isn't visible on the page violates Google's guidelines — structured data must reflect visible content. Using incorrect types (e.g., Product for a service) can result in manual actions. Leaving required properties empty or using placeholder values reduces trust signals. Not keeping structured data in sync with visible content after page updates. ### Validation and Testing Use Google's Rich Results Test for individual pages and the Schema Markup Validator for comprehensive validation. After implementing schema, monitor the Enhancements reports in Google Search Console for errors and warnings. Rich results may take weeks to appear after implementation — be patient and verify the data is correct. ### EXIF Data Privacy: What Your Photos Reveal Understand what metadata your camera stores in photos and how to strip it before sharing for privacy protection. - URL: https://peasyseo.com/guides/exif-data-privacy-what-photos-reveal/ - Category: How-To - Reading time: 1 min - Words: 299 ## EXIF Photo Metadata Privacy Every photo your smartphone or camera takes embeds metadata that can reveal your exact location, device model, the time it was taken, and even your name. Understanding this metadata helps you protect your privacy when sharing photos. ### What EXIF Contains Camera make and model, lens information, shutter speed, aperture, ISO, focal length, white balance, flash status. GPS coordinates (latitude, longitude, altitude) accurate to within a few meters. Date and time of capture. Thumbnail preview image. Software used for editing. Copyright information. On smartphones: device serial number and sometimes Wi-Fi network name. ### Privacy Risks GPS coordinates in shared photos can reveal your home address, workplace, children's school, and daily routine. This information has been used in stalking, burglary (knowing when you're away), and doxxing. Even photos taken indoors contain GPS data. Social media platforms like Twitter/X and Facebook strip GPS data on upload, but many other platforms (forums, messaging apps, cloud storage) do not. ### Stripping EXIF Data Browser-based tools process images locally, removing all metadata while preserving the image quality. Upload photos, select which metadata to strip (all, GPS only, or custom selection), and download the cleaned versions. The image pixels are untouched — only the metadata wrapper is modified. ### Selective Metadata Preservation Sometimes you want to keep camera settings (for photography portfolios) while removing GPS data. Most EXIF stripping tools offer selective removal. Preserve: camera model, exposure settings, lens info. Remove: GPS coordinates, date/time, thumbnails, device identifiers, editing software traces. ### Prevention Settings On iPhone: Settings → Privacy → Location Services → Camera → set to "Never." On Android: Camera app settings → Location/GPS tagging → Off. This prevents GPS data from being embedded in future photos. For photos already taken, you need to strip the metadata after the fact. ### International SEO: hreflang Tags and Multi-Language Sites Serving content in multiple languages requires careful SEO configuration to ensure the right version appears in the right country's search results. - URL: https://peasyseo.com/guides/international-seo-hreflang-multi-language/ - Category: Best Practice - Reading time: 1 min - Words: 234 ## The hreflang Challenge When you have the same content in multiple languages, search engines need to know which version to show to which users. Without hreflang tags, Google may show the English version to French users or consider your translations as duplicate content. ### hreflang Syntax Each page must reference all language versions, including itself. The format is: `<link rel="alternate" hreflang="fr" href="https://example.com/fr/page/">` for French, and `<link rel="alternate" hreflang="x-default" href="https://example.com/page/">` as a fallback for unmatched languages. ### Common Implementation Errors The most frequent error is non-reciprocal hreflang — Page A references Page B, but Page B doesn't reference Page A. Google requires reciprocal references to validate the relationship. Another common error is using incorrect language codes — use ISO 639-1 (two-letter) codes, and include the country code when targeting specific regions (e.g., `pt-BR` for Brazilian Portuguese vs `pt-PT` for European Portuguese). ### URL Structure Options Subdirectories (`/fr/`, `/de/`) are the simplest to manage and keep all content under one domain's authority. Subdomains (`fr.example.com`) are easier to host separately but dilute domain authority. Separate domains (`example.fr`) provide the strongest geo-targeting signal but require building authority for each domain independently. ### Content Strategy Direct translation is rarely sufficient — localize content for the target market. Currency, measurements, cultural references, and legal requirements vary by region. Ensure translated URLs use localized slugs: `/fr/guide-seo/` not `/fr/seo-guide/`. Don't translate boilerplate content (navigation, footers) without also translating the main content. ### SEO Competitor Backlink Analysis Guide Analyze competitor backlink profiles to discover link-building opportunities for your site. - URL: https://peasyseo.com/guides/seo-competitor-backlink-analysis-guide/ - Category: How-To - Reading time: 1 min - Words: 257 Key takeaways: - Understanding where your competitors get their links reveals opportunities you're missing. - Start with the top 5 ranking pages for your primary keywords. - For each competitor, examine total referring domains (not just total links), domain authority distribution, link type breakdown (editorial, directory, forum, comment), and anchor text patterns. - The backlink gap shows domains linking to competitors but not you. - For each opportunity, identify the right contact person (editor, webmaster, author). ## Why Analyze Competitor Backlinks Understanding where your competitors get their links reveals opportunities you're missing. If a site links to three competitors but not you, that's a warm outreach target. Backlink gap analysis is one of the most efficient ways to build a link acquisition strategy. ## Building Your Competitor List Start with the top 5 ranking pages for your primary keywords. Note which domains consistently appear. These are your true SEO competitors — they may differ from your business competitors. Include both direct competitors and informational sites that rank for your target terms. ## Analyzing Link Profiles For each competitor, examine total referring domains (not just total links), domain authority distribution, link type breakdown (editorial, directory, forum, comment), and anchor text patterns. Focus on links from domains with actual traffic — a link from a high-traffic blog is worth more than hundreds from low-quality directories. ## Finding Link Opportunities The backlink gap shows domains linking to competitors but not you. Prioritize domains linking to multiple competitors — they're clearly willing to link to sites in your niche. Resource pages, roundup posts, and broken link opportunities are the easiest to replicate. Guest posting opportunities appear when competitors have authored content on other sites. ## Outreach Strategy For each opportunity, identify the right contact person (editor, webmaster, author). Personalize your outreach — reference specific content on their site. Offer genuine value — a better resource, updated data, or unique perspective. Follow up once after 5-7 days. Track your outreach in a spreadsheet with dates, responses, and outcomes. ### SEO for Single-Page Applications and JavaScript-Heavy Sites SPAs present unique SEO challenges because content is rendered by JavaScript. Learn how to ensure search engines can discover and index your dynamically generated content. - URL: https://peasyseo.com/guides/seo-single-page-applications-javascript/ - Category: How-To - Reading time: 2 min - Words: 302 ## The SPA Indexing Problem Traditional websites serve complete HTML that search engines can immediately parse. Single-page applications serve a minimal HTML shell and use JavaScript to load and render content. While Googlebot executes JavaScript, it's slower and less reliable than parsing static HTML. ### Server-Side Rendering (SSR) SSR generates complete HTML on the server for each request. The browser receives fully rendered content, and JavaScript then "hydrates" it to add interactivity. This gives search engines immediate access to content while preserving the SPA experience. Next.js, Nuxt.js, and SvelteKit provide SSR out of the box. ### Static Site Generation (SSG) For content that doesn't change per-request, SSG pre-renders pages at build time. Pages are served as static HTML — the fastest possible delivery. Ideal for blogs, documentation, and marketing pages. Rebuild when content changes. Works with any CDN and requires no server-side runtime. ### Dynamic Rendering For legacy SPAs that can't easily add SSR, dynamic rendering serves pre-rendered HTML to search engine bots while serving the SPA to regular users. This is a temporary workaround, not a long-term strategy. Google has stated it will eventually deprecate support for dynamic rendering. ### Critical SEO Elements for SPAs Ensure unique `<title>` and meta description tags for each route. Update `<title>` and meta tags on client-side route changes (not just on initial load). Implement canonical URLs for each route. Generate a dynamic XML sitemap listing all routes. Use internal links (`<a href>`) rather than JavaScript click handlers for navigation — Google follows `<a>` tags more reliably than JavaScript navigation. ### Monitoring Indexing Use Google Search Console's URL Inspection tool to see how Google renders your pages. Check for missing content, broken JavaScript, and render errors. Compare the rendered HTML to what a browser shows. Monitor the Coverage report for indexing errors specific to … ### PDF Security Best Practices for Business Documents Business documents often contain sensitive information. Learn how to secure PDFs with encryption, redaction, and metadata removal. - URL: https://peasyseo.com/guides/pdf-security-best-practices/ - Category: Best Practice - Reading time: 1 min - Words: 177 Key takeaways: - Before applying security measures, classify your documents. - A common mistake is 'hiding' sensitive text by placing a black rectangle over it. - PDFs store metadata that can reveal sensitive information: author name, company name, creation software, edit history, and GPS coordinates (for scanned photos). - Digital signatures using PKI certificates prove the document's authenticity and detect any modifications after signing. - For the highest security, combine encryption with distribution tracking. ## Document Classification Before applying security measures, classify your documents. Public documents need minimal protection. Internal documents should have basic access controls. Confidential documents require encryption, and restricted documents need the highest level of protection. ## Redaction vs Hiding A common mistake is 'hiding' sensitive text by placing a black rectangle over it. This does not remove the text — it can be revealed by selecting and copying. True redaction permanently removes the underlying text, replacing it with blank space. ## Metadata Cleaning PDFs store metadata that can reveal sensitive information: author name, company name, creation software, edit history, and GPS coordinates (for scanned photos). Always strip metadata from documents shared externally. ## Digital Signatures Digital signatures using PKI certificates prove the document's authenticity and detect any modifications after signing. They're legally binding in most jurisdictions and essential for contracts, regulatory filings, and official communications. ## Distribution Controls For the highest security, combine encryption with distribution tracking. Add unique watermarks to each copy with the recipient's name, making it possible to trace leaks back to the source. ### On-Page SEO vs Technical SEO: Understanding the Difference Compare on-page content optimization with technical SEO infrastructure for balanced search strategy. - URL: https://peasyseo.com/guides/on-page-seo-vs-technical-seo-comparison/ - Category: Comparison - Reading time: 1 min - Words: 261 Key takeaways: - On-page SEO focuses on content and HTML elements visible to users and search engines — title tags, headings, content quality, internal linking, and keyword optimization. - Title tags should include primary keywords within 60 characters. - Core Web Vitals (LCP, INP, CLS) directly impact rankings. - If your site has crawling or indexing issues, technical SEO must come first — great content that can't be indexed won't rank. - Start with a technical audit: check indexing status, crawl errors, page speed, mobile usability, and structured data validation. ## Two Pillars of SEO On-page SEO focuses on content and HTML elements visible to users and search engines — title tags, headings, content quality, internal linking, and keyword optimization. Technical SEO addresses the infrastructure that enables crawling and indexing — site speed, mobile-friendliness, XML sitemaps, structured data, and crawl budget management. ## On-Page SEO Essentials Title tags should include primary keywords within 60 characters. Meta descriptions serve as ad copy in search results (155-160 characters). H1 tags should match search intent. Content should comprehensively address the topic with proper heading hierarchy. Internal links distribute authority and help users navigate. Image alt text provides context for search engines and accessibility. ## Technical SEO Fundamentals Core Web Vitals (LCP, INP, CLS) directly impact rankings. Mobile-first indexing means your mobile site is what Google evaluates. XML sitemaps help search engines discover pages efficiently. Robots.txt controls crawl access. HTTPS is a ranking signal. Canonical tags prevent duplicate content issues. Structured data (Schema.org) enables rich results. ## Which to Prioritize If your site has crawling or indexing issues, technical SEO must come first — great content that can't be indexed won't rank. If your site is technically sound but content is thin or poorly optimized, on-page improvements will have more impact. Most sites need both working together. ## Audit Approach Start with a technical audit: check indexing status, crawl errors, page speed, mobile usability, and structured data validation. Then audit on-page elements: title tags, content quality, keyword targeting, internal linking structure. Create a prioritized action plan addressing critical technical issues first, then systematic on-page optimization. ### Internal Linking Strategy for SEO Impact Build an effective internal linking structure to distribute page authority and improve rankings. - URL: https://peasyseo.com/guides/internal-linking-strategy-seo-impact/ - Category: Best Practice - Reading time: 1 min - Words: 266 Key takeaways: - Internal links are the most underutilized SEO tool. - Organize content into topic clusters with a central hub page linking to detailed spoke pages. - Use descriptive anchor text that includes relevant keywords — not generic "click here" or "learn more." Vary anchor text naturally across links pointing to the same page. - Add contextual links within body content — these carry the most weight. - Identify orphan pages (no internal links pointing to them) — these are nearly invisible to search engines. ## The Power of Internal Links Internal links are the most underutilized SEO tool. Unlike external links, you have complete control over anchor text, placement, and link structure. Strategic internal linking distributes page authority (PageRank), helps search engines understand content relationships, and improves user navigation. ## Hub and Spoke Model Organize content into topic clusters with a central hub page linking to detailed spoke pages. The hub targets broad keywords while spokes target specific long-tail queries. Each spoke links back to the hub and to related spokes. This structure signals topical authority to search engines. ## Anchor Text Best Practices Use descriptive anchor text that includes relevant keywords — not generic "click here" or "learn more." Vary anchor text naturally across links pointing to the same page. Match the anchor text to the target page's primary keyword or topic. Avoid over-optimization by using a mix of exact match, partial match, and branded anchors. ## Implementation Techniques Add contextual links within body content — these carry the most weight. Use breadcrumb navigation for hierarchical content. Include related content sections at the end of articles. Create comprehensive resource pages that link to all relevant content. Update older content with links to newer related pages. ## Auditing Internal Links Identify orphan pages (no internal links pointing to them) — these are nearly invisible to search engines. Find pages with excessive links (diluting value). Check for broken internal links. Use crawl tools to visualize your site's link graph. Prioritize linking to pages that are close to ranking (positions 5-15) — a few internal links can push them onto page one. ### PDF Metadata and Document Properties Guide Manage PDF metadata including title, author, keywords, and custom properties for organization and discoverability. - URL: https://peasyseo.com/guides/pdf-metadata-document-properties/ - Category: How-To - Reading time: 1 min - Words: 284 Key takeaways: - PDF metadata — title, author, subject, keywords, and creation date — serves both organizational and SEO purposes. - Title is the most important — it appears in browser tabs, search results, and document management systems. - Never leave it as the filename. ## PDF Metadata Management PDF metadata — title, author, subject, keywords, and creation date — serves both organizational and SEO purposes. Properly tagged PDFs are easier to find, catalog, and manage in document management systems. ### Standard Metadata Fields The PDF specification defines standard metadata fields in the Document Information Dictionary: Title, Author, Subject, Keywords, Creator (the application that created the source), Producer (the application that generated the PDF), CreationDate, and ModDate. Title is the most important — it appears in browser tabs, search results, and document management systems. Never leave it as the filename. ### XMP Metadata Modern PDFs support XMP (Extensible Metadata Platform), an XML-based metadata format that supports richer information: copyright status, licensing terms, rights management, and custom schemas. XMP metadata is stored in a separate stream within the PDF and can include structured data that the Document Information Dictionary cannot represent. ### Metadata for Discoverability Search engines index PDF metadata. A PDF with a descriptive title, relevant keywords, and a clear subject ranks better than one with "Document1.pdf" as its title. For academic papers, include DOI, ISSN, and author affiliations. For business documents, include department, classification level, and document number. ### Bulk Metadata Management For large document collections, use command-line tools to read, update, or standardize metadata across hundreds of PDFs. Common operations include setting the author field consistently, updating copyright years, and applying keyword taxonomies. Automation prevents the inconsistencies that manual metadata entry inevitably produces. ### Privacy Implications PDF metadata can reveal information you don't intend to share: the author's full name, the organization, the software used, and revision history. Before publishing PDFs externally, review and sanitize metadata. Remove tracked changes, comments, hidden text layers, and previous revision metadata. ### How to Redact Sensitive Information in PDFs Permanently remove confidential text, images, and metadata from PDF documents before sharing. - URL: https://peasyseo.com/guides/how-to-redact-sensitive-info-pdfs/ - Category: How-To - Reading time: 2 min - Words: 311 ## PDF Redaction Redaction permanently removes sensitive content from PDFs. Unlike placing a black rectangle over text (which is cosmetic — the text remains selectable underneath), proper redaction deletes the underlying data. ### The Difference Between Covering and Redacting Drawing a black box over text in a PDF editor only hides the content visually. The text remains in the file and can be extracted by copying, searching, or using PDF parsing tools. Actual redaction replaces the text with a blank area and removes the character data from the file's content stream. Several high-profile data leaks have resulted from cosmetic redaction rather than actual redaction. ### Redaction Process Mark areas for redaction (text passages, images, form field data), then apply the redactions in a separate step. This two-step process lets you review marks before committing — redaction is irreversible. After applying, verify the redaction by searching for the original text and by examining the file with a PDF text extraction tool. ### Metadata Redaction PDF files contain metadata beyond the visible content: author name, creation date, revision history, comments, hidden annotations, and embedded file attachments. Use a metadata sanitization step after content redaction. Some PDFs also contain thumbnail images that may show pre-redacted content. ### Browser-Based Redaction Tools Client-side PDF redaction tools process the document entirely in your browser. Upload the PDF, mark areas for redaction, apply, and download the result. Since the file never leaves your device, this is suitable for confidential documents. Verify the output by attempting to select text in the redacted areas — properly redacted content should not be selectable. ### Legal and Compliance Requirements GDPR right-to-erasure requests may require redacting personal data from stored PDFs. FOIA (Freedom of Information Act) responses use redaction extensively. Court documents require certified redaction processes. In regulated industries, document your redaction … ### Image Metadata: EXIF, IPTC, and XMP Explained Digital images contain hidden metadata that reveals camera settings, location data, and copyright information. Understand the three major metadata standards and how to manage them. - URL: https://peasyseo.com/guides/image-metadata-exif-iptc-xmp/ - Category: Best Practice - Reading time: 1 min - Words: 244 ## Three Metadata Standards Digital images can contain metadata in three overlapping standards, each with different origins and strengths. ### EXIF (Exchangeable Image File Format) EXIF data is written by cameras and smartphones at capture time. It records technical settings: aperture, shutter speed, ISO, focal length, flash status, date/time, and GPS coordinates. EXIF is limited to JPEG and TIFF formats. It cannot be easily extended with custom fields. ### IPTC (International Press Telecommunications Council) IPTC metadata was designed for news photography workflows. It stores descriptive information: caption, photographer name, copyright notice, keywords, location name, and usage rights. IPTC fields are standardized across the industry, making them the foundation of stock photography metadata. ### XMP (Extensible Metadata Platform) Adobe's XMP format uses XML to store metadata that can be extended with custom schemas. XMP can contain all EXIF and IPTC data plus application-specific data like Lightroom develop settings, Photoshop layer information, and custom workflows. XMP works with virtually any file format. ### Privacy Considerations GPS coordinates in EXIF data can reveal your home address, workplace, and daily patterns. Before sharing images online, strip location data and any other personally identifying metadata. Camera serial numbers and lens identifiers can also be used to track photographers across images. ### Metadata Preservation During Conversion Not all format converters preserve metadata. When converting between formats, verify that essential metadata (copyright, description, keywords) survives the conversion. JPEG to WebP conversions often strip EXIF data unless explicitly configured to preserve it. ### Best Practices for Writing SEO-Friendly Meta Descriptions Meta descriptions are your page's elevator pitch in search results. Well-crafted descriptions improve click-through rates without directly affecting rankings. This guide covers optimal length, keyword placement, and persuasion techniques. - URL: https://peasyseo.com/guides/best-practices-seo-friendly-meta-descriptions/ - Category: Best Practice - Reading time: 3 min - Words: 526 Key takeaways: - Meta descriptions don't directly influence search engine rankings — Google confirmed this in 2009. - Google displays approximately 155-160 characters of the meta description on desktop and 120-130 characters on mobile. - Start with what the user gets, not who you are. - Cramming multiple keyword variations into 160 characters creates unreadable descriptions that users skip over. - Use Google Search Console to monitor CTR by page. ## What Meta Descriptions Actually Do Meta descriptions don't directly influence search engine rankings — Google confirmed this in 2009. However, they significantly affect click-through rate (CTR), which indirectly influences rankings through user engagement signals. A compelling meta description can double your CTR compared to a generic or auto-generated one, driving substantially more traffic from the same ranking position. ## Optimal Length ### Desktop vs Mobile Google displays approximately 155-160 characters of the meta description on desktop and 120-130 characters on mobile. Write your most important message in the first 120 characters to ensure it's visible across all devices. The remaining characters are bonus space for desktop users. ### Pixel Width Matters More Than Character Count Google actually truncates based on pixel width (approximately 920 pixels on desktop), not character count. Narrow characters like 'i' and 'l' take less space than wide characters like 'W' and 'M'. A description with many wide characters may get truncated at 140 characters, while one with narrow characters might display 170 characters. ## Writing Effective Descriptions ### Lead with Value Start with what the user gets, not who you are. Instead of 'PeasyTools is an online tool suite that offers...' write 'Convert PDF to Word in seconds — free, no signup, processed entirely in your browser.' The value proposition should be immediately clear. ### Include a Call to Action End with a gentle CTA that creates urgency or curiosity: 'Try it free,' 'No signup required,' 'See how it works,' or 'Compare options.' CTAs increase CTR by 15-20% on average compared to descriptions without them. ### Use Keywords Naturally Google bolds search query terms in the meta description, making matching keywords visually prominent. Include your target keyword phrase naturally — forcing it reads poorly and can actually reduce CTR. If the keyword appears in the … ### Audio Metadata and ID3 Tags: A Complete Reference Audio metadata — embedded information about title, artist, album, artwork, and more — determines how music appears in players, libraries, and streaming services. Proper tagging prevents misidentified tracks and missing artwork. - URL: https://peasyseo.com/guides/audio-metadata-id3-tags-guide/ - Category: How-To - Reading time: 2 min - Words: 342 ## Metadata Standards by Format | Format | Metadata Container | Common Fields | |--------|-------------------|---------------| | MP3 | ID3v2.3 / ID3v2.4 | Title, Artist, Album, Year, Track, Genre, Art | | FLAC | Vorbis Comments | Same fields, different container | | AAC/M4A | MP4 Atoms (iTunes-style) | Same fields, plus Apple-specific tags | | OGG | Vorbis Comments | Same as FLAC | | WAV | RIFF INFO / ID3 | Limited support, inconsistent | ## Essential Tags ### For Music - **Title** — Song name (avoid ALL CAPS or special characters) - **Artist** — Performing artist (consistent spelling across albums) - **Album Artist** — For compilations, the album-level artist - **Album** — Album name (consistent across all tracks) - **Track Number** — Format as 'N/Total' (e.g., 3/12) - **Disc Number** — For multi-disc albums (1/2, 2/2) - **Year** — Release year (four digits: 2026) - **Genre** — Primary genre (one, not a list) - **Album Art** — Embedded JPEG, 500×500 to 1500×1500 pixels ### For Podcasts - **Title** — Episode title including episode number - **Artist** — Show name or host name - **Album** — Podcast show name - **Track Number** — Episode number - **Comment** — Episode description/show notes - **Genre** — 'Podcast' - **Album Art** — Show artwork (3000×3000 for Apple Podcasts) ## Album Art Specifications | Platform | Minimum Size | Recommended | Max File Size | |----------|-------------|-------------|---------------| | Apple Music | 1400×1400 | 3000×3000 | 10 MB | | Spotify | 640×640 | 3000×3000 | 10 MB | | Embedded (MP3) | 300×300 | 500×500 | 500 KB | ## Common Tagging Mistakes - **Inconsistent artist names** — 'The Beatles' vs 'Beatles, The' creates duplicate entries in music libraries - **Missing album artist** — Compilation tracks appear under individual artists instead of grouped together … ### Data Serialization Formats: JSON, YAML, TOML, XML, and Protocol Buffers Compare data serialization formats for configuration files, API responses, and inter-service communication. Understand parsing performance, human readability, and schema validation capabilities. - URL: https://peasyseo.com/guides/data-serialization-json-yaml-toml-xml-protobuf/ - Category: Best Practice - Reading time: 1 min - Words: 269 Key takeaways: - Serialization formats divide into human-readable text formats (JSON, YAML, TOML, XML) and binary formats (Protocol Buffers, MessagePack, CBOR). - JSON's simplicity and universal language support make it the default for APIs and data interchange. - YAML supports comments, anchors, multi-line strings, and rich data types. - JSON**: APIs, data interchange, structured storage ## Human-Readable vs Binary Formats Serialization formats divide into human-readable text formats (JSON, YAML, TOML, XML) and binary formats (Protocol Buffers, MessagePack, CBOR). Text formats prioritize debuggability and editability. Binary formats prioritize parsing speed and compact wire size. ## Text Format Comparison | Feature | JSON | YAML | TOML | XML | | --- | --- | --- | --- | --- | | Comments | No | Yes | Yes | Yes | | Multi-line strings | No (escaped) | Yes | Yes | CDATA | | Data types | 6 types | Rich | Typed | String-based | | Nesting | Braces | Indentation | Tables/sections | Tags | | Trailing commas | No | N/A | No | N/A | | Parse speed | Fast | Slow | Fast | Medium | ## JSON: The API Standard JSON's simplicity and universal language support make it the default for APIs and data interchange. Its limitations — no comments, no trailing commas, no multi-line strings — make it less ideal for human-edited configuration files but excellent for machine-generated data. ## YAML: Powerful but Dangerous YAML supports comments, anchors, multi-line strings, and rich data types. However, its flexibility creates foot-guns: `on` and `off` are booleans, `1.0` can be a float or a string depending on context, and indentation errors cause silent data corruption rather than parse failures. ## Choosing Your Format - **JSON**: APIs, data interchange, structured storage - **TOML**: Application configuration files - **YAML**: Kubernetes manifests, CI/CD pipelines (where the ecosystem demands it) - **XML**: Document markup, legacy systems, SOAP APIs - **Protocol Buffers**: High-performance microservice communication ### JSON Formatting and Validation: Best Practices for Clean Data Best practices for formatting, validating, and structuring JSON data. Covers indentation standards, JSON Schema validation, common syntax errors, and the differences between JSON and JSON5. - URL: https://peasyseo.com/guides/json-formatting-validation-best-practices/ - Category: Best Practice - Reading time: 1 min - Words: 268 Key takeaways: - JSON has a single universal syntax — no competing standards or flavors. - Trailing comma**: `{"a": 1,}` — invalid in JSON (valid in JS/JSON5) - JSON Schema defines the expected structure, types, and constraints of your JSON data. - JSON5 relaxes JSON's strict syntax — allowing comments, trailing commas, single quotes, and unquoted keys. - For data interchange, always use standard JSON. ## JSON Formatting Standards JSON has a single universal syntax — no competing standards or flavors. Yet formatting varies widely: minified for production, pretty-printed for debugging, and sorted keys for deterministic output. Consistent formatting prevents unnecessary diff noise in version control. ## Formatting Conventions | Convention | When | Benefit | | --- | --- | --- | | 2-space indent | Most codebases | Compact, readable | | 4-space indent | Python ecosystems | Extra readability | | Sorted keys | Config files, snapshots | Deterministic diffs | | Minified | API responses, storage | Minimal size | | One item per line | Arrays of objects | Clean diffs | ## Common Syntax Errors - **Trailing comma**: `{"a": 1,}` — invalid in JSON (valid in JS/JSON5) - **Single quotes**: `{'a': 1}` — invalid, must use double quotes - **Unquoted keys**: `{a: 1}` — invalid, keys must be quoted strings - **Comments**: `// comment` — not allowed in JSON - **Infinity/NaN**: Not valid JSON values ## JSON Schema Validation JSON Schema defines the expected structure, types, and constraints of your JSON data. It catches type errors (`string` where `number` expected), missing required fields, and invalid enum values before they cause runtime failures. Use schemas for API request/response validation and configuration file validation. ## JSON5 and Alternatives JSON5 relaxes JSON's strict syntax — allowing comments, trailing commas, single quotes, and unquoted keys. It is popular for configuration files that humans edit directly. For data interchange, always use standard JSON. Format, validate, and transform JSON with the Peasy JSON tools — supports pretty-printing, minification, sorting, and JSON Schema validation. ### Secure Messaging Apps Compared: Signal, WhatsApp, Telegram, and More An objective comparison of popular messaging apps focusing on encryption protocols, metadata handling, open-source status, and jurisdiction. Understand the real-world security differences beyond marketing claims. - URL: https://peasyseo.com/guides/secure-messaging-apps-compared/ - Category: Best Practice - Reading time: 1 min - Words: 279 Key takeaways: - Most major messaging apps now offer end-to-end encryption, but their security postures differ dramatically in metadata collection, backup encryption, group chat implementation, and corporate incentive structures. - Signal collects only your phone number and registration date. - Telegram is often perceived as a secure messenger, but standard chats are not end-to-end encrypted — they use client-server encryption. - For maximum security, use Signal. ## Encryption Is Not the Whole Story Most major messaging apps now offer end-to-end encryption, but their security postures differ dramatically in metadata collection, backup encryption, group chat implementation, and corporate incentive structures. A messaging app that encrypts messages but stores contact graphs and timestamps still reveals significant information. ## Feature Comparison | Feature | Signal | WhatsApp | Telegram | iMessage | | --- | --- | --- | --- | --- | | E2EE default | Yes | Yes | No (opt-in) | Yes | | Protocol | Signal | Signal | MTProto | Custom | | Open source | Full | Client only | Client only | No | | Metadata collected | Minimal | Extensive | Moderate | Moderate | | Backup encryption | Yes | Optional | Server-side | iCloud | | Group E2EE | Yes | Yes | No | Yes | ## Signal: The Gold Standard Signal collects only your phone number and registration date. Message content, contact lists, group memberships, and profile information are all encrypted. The server code is open source and regularly audited. Signal is operated by a nonprofit foundation with no advertising business model. ## The Telegram Misconception Telegram is often perceived as a secure messenger, but standard chats are not end-to-end encrypted — they use client-server encryption. Only Secret Chats enable E2EE, and these do not work in groups. Telegram stores message content on its servers, accessible with the encryption keys it holds. ## Making Your Choice For maximum security, use Signal. For convenience with adequate security, WhatsApp with encrypted backups is a reasonable compromise. Avoid relying on Telegram for sensitive communications unless using Secret Chats exclusively. ### Database Export Formats: SQL, CSV, JSON, and Parquet Choose the right export format for database migrations, analytics, and data sharing. Understand the tradeoffs between portability, performance, schema preservation, and human readability. - URL: https://peasyseo.com/guides/database-export-formats-sql-csv-json-parquet/ - Category: Best Practice - Reading time: 1 min - Words: 266 Key takeaways: - Database exports serve different purposes — migrations require schema and data fidelity, analytics need columnar efficiency, and sharing demands universal readability. - SQL dumps preserve everything — schemas, constraints, indexes, sequences, and data. - Apache Parquet stores data in columnar format with per-column compression and type encoding. - Same-engine migration**: SQL dump (pg_dump, mysqldump) ## Export Format Tradeoffs Database exports serve different purposes — migrations require schema and data fidelity, analytics need columnar efficiency, and sharing demands universal readability. No single format excels at everything. ## Format Comparison | Feature | SQL Dump | CSV | JSON | Parquet | | --- | --- | --- | --- | --- | | Schema included | Yes | No | Flexible | Yes (typed) | | Data types | Full | Strings only | Basic (6 types) | Rich | | Relationships | Yes (FK) | No | Nested | No | | Compression | No (text) | No (text) | No (text) | Built-in (columnar) | | Human readable | Yes | Yes | Yes | No (binary) | | Query without import | No | Limited | Limited | Yes (DuckDB, Polars) | ## SQL Dump: Full Fidelity SQL dumps preserve everything — schemas, constraints, indexes, sequences, and data. They are the standard for database-to-database migration within the same engine. Cross-engine compatibility is limited; PostgreSQL dumps do not import cleanly into MySQL without modification. ## Parquet: The Analytics Standard Apache Parquet stores data in columnar format with per-column compression and type encoding. A 1GB CSV file typically compresses to 100-200MB as Parquet while being dramatically faster to query. Tools like DuckDB, Polars, and pandas can query Parquet files directly without importing into a database. ## Choosing Your Format - **Same-engine migration**: SQL dump (pg_dump, mysqldump) - **Cross-engine migration**: CSV + separate schema DDL - **Analytics/data science**: Parquet - **API data exchange**: JSON - **Human review**: CSV or formatted SQL ### API Mock Data Generation for Frontend Development Frontend developers often need to work before the backend API is ready. Mock data generators create realistic API responses that match the expected schema, enabling parallel development. - URL: https://peasyseo.com/guides/api-mock-data-generation/ - Category: Best Practice - Reading time: 1 min - Words: 289 Key takeaways: - Waiting for the backend to be complete before starting frontend work wastes time. - The simplest approach: create JSON files that mirror expected API responses. - Good mock servers simulate failure modes: - Cons: Setup overhead, must maintain mocks. - Pros: Always in sync with API contract. ## Why Mock APIs Waiting for the backend to be complete before starting frontend work wastes time. Mock APIs decouple the two teams, allowing parallel development with agreed-upon contracts (schemas). ## Approaches ### 1. Static JSON Files The simplest approach: create JSON files that mirror expected API responses. Serve them with a static file server or import directly in code. **Pros**: Zero setup, version-controlled. **Cons**: No dynamic behavior, stale quickly. ### 2. Mock Server Tools like MSW (Mock Service Worker), JSON Server, or Prism intercept API requests and return mock responses. MSW runs in the browser's service worker — no separate server process needed. **Pros**: Realistic network behavior, error simulation. **Cons**: Setup overhead, must maintain mocks. ### 3. Schema-Driven Generation Define your API with OpenAPI (Swagger) and use tools that auto-generate mock data from the schema. Libraries like Faker.js can populate schema-defined types with realistic values. **Pros**: Always in sync with API contract. **Cons**: Requires upfront schema definition. ## Mock Data Quality | Aspect | Bad Mock | Good Mock | |--------|---------|----------| | Names | 'Test User 1' | 'Alejandra Moreno' | | Dates | '2020-01-01' everywhere | Varied realistic dates | | IDs | 1, 2, 3 | UUIDs or realistic ID formats | | Lists | Always 3 items | Varying lengths (0, 1, 5, 20) | | Errors | Never tested | Include 404, 500, timeout scenarios | ## Error and Edge Case Simulation Good mock servers simulate failure modes: - Slow responses (add artificial latency) - Empty results (no data state) - Paginated results with varying page sizes - Authentication errors (401, 403) - Server errors (500, 503) - Network timeout Testing against these scenarios in development catches error handling bugs before they reach production. ### SVG Optimization for Web: Reducing File Size and Complexity SVG files exported from design tools contain redundant metadata, unnecessary precision, and editor artifacts. Optimization can reduce file size by 20-60% without any visual change. - URL: https://peasyseo.com/guides/svg-optimization-for-web/ - Category: How-To - Reading time: 1 min - Words: 274 Key takeaways: - Design tools like Figma, Illustrator, and Sketch embed editor metadata, redundant namespaces, excessive decimal precision, and hidden layers in exported SVGs. - SVGO (SVG Optimizer) is the industry-standard tool. - Complex paths with hundreds of anchor points can often be simplified without visible change. - For icons used across many pages, an SVG sprite sheet offers the best balance of performance and flexibility. ## Why Optimize SVGs Design tools like Figma, Illustrator, and Sketch embed editor metadata, redundant namespaces, excessive decimal precision, and hidden layers in exported SVGs. A 50KB logo might shrink to 15KB after optimization — a significant saving when the icon appears on every page. ## What SVGO Removes SVGO (SVG Optimizer) is the industry-standard tool. Its default plugins remove: - XML declarations and doctype - Editor metadata (Illustrator, Sketch namespaces) - Empty groups and unused definitions - Redundant attributes inherited from parents - Excessive coordinate precision (6 decimals reduced to 1-2) - Comments and hidden elements ## Manual Optimization Techniques ### Simplify Paths Complex paths with hundreds of anchor points can often be simplified without visible change. In Illustrator, use Object > Path > Simplify before exporting. This reduces both file size and rendering cost. ### Use CSS Instead of Attributes Inline `fill`, `stroke`, and `opacity` attributes can be consolidated into a `<style>` block or external CSS. This enables theming (including dark mode) and reduces repetition across similar elements. ### Avoid Embedded Rasters Some SVGs contain embedded PNG or JPEG data (base64-encoded `<image>` elements). These negate the scalability benefit of SVG. Extract raster elements into separate files or recreate them as vector paths. ## Inline vs External SVGs | Method | Pros | Cons | |--------|------|------| | Inline `<svg>` | No HTTP request, CSS-stylable | Increases HTML size, not cached | | External `<img>` | Cached, clean HTML | Not CSS-stylable, extra request | | SVG sprite | Cached, CSS-stylable | Build step required | For icons used across many pages, an SVG sprite sheet offers the best balance of performance and flexibility. ### Image Metadata and EXIF Data: Reading, Editing, and Removing Every photo carries hidden metadata — camera settings, GPS coordinates, timestamps, and software information. Understanding how to read, edit, and strip this data is essential for privacy, SEO, and digital asset management. - URL: https://peasyseo.com/guides/image-metadata-exif-editing-guide/ - Category: How-To - Reading time: 2 min - Words: 339 Key takeaways: - EXIF (Exchangeable Image File Format) is a standard for storing metadata inside image files. - Photos taken at home embed your home address as GPS coordinates. - Remove EXIF data before sharing images publicly — especially GPS coordinates, timestamps, and device information. - Keep EXIF data when archiving photos for personal use, submitting to stock photography platforms (they use camera data for categorization), or maintaining a professional portfolio where camera settings demonstrate technical skill. - The best approach is often selective: remove GPS and personal data while preserving copyright notices and technical camera settings. ## What Is EXIF Data? EXIF (Exchangeable Image File Format) is a standard for storing metadata inside image files. When you take a photo with a smartphone or DSLR, the camera embeds dozens of data fields: shutter speed, aperture, ISO, focal length, date/time, GPS coordinates, camera make and model, and even the lens serial number. ## Common EXIF Fields | Field | Example Value | Privacy Risk | |-------|--------------|-------------| | GPS Latitude/Longitude | 37.7749, -122.4194 | High | | DateTime Original | 2026:03:10 14:30:00 | Medium | | Camera Make/Model | Apple iPhone 16 Pro | Low | | Software | Adobe Photoshop 2026 | Low | | Author/Copyright | John Doe Photography | Low | | Thumbnail | Embedded preview | Medium | ## Privacy Concerns ### GPS Data Risks Photos taken at home embed your home address as GPS coordinates. Sharing these photos on forums, marketplaces, or personal websites can inadvertently reveal your location. Most social media platforms strip EXIF data on upload, but direct file sharing (email, Slack, cloud storage links) preserves it. ### Embedded Thumbnails Some image editors update the main image but leave the original embedded thumbnail unchanged. If you crop a photo to remove sensitive content, the uncropped version may still be visible in the EXIF thumbnail. ## When to Strip EXIF Remove EXIF data before sharing images publicly — especially GPS coordinates, timestamps, and device information. Strip all metadata from images uploaded to websites to reduce file size (EXIF data can add 10-50 KB per image). ## When to Preserve EXIF Keep EXIF data when archiving photos for personal use, submitting to stock photography platforms (they use camera data for categorization), or maintaining a professional portfolio where camera settings demonstrate technical skill. Copyright and attribution fields should be preserved whenever possible. ## Selective … ### Technical SEO Audit Checklist for Web Developers A technical SEO audit identifies crawlability, indexability, and performance issues that prevent search engines from properly ranking your site. This checklist covers the most impactful items. - URL: https://peasyseo.com/guides/technical-seo-audit-checklist/ - Category: Best Practice - Reading time: 2 min - Words: 300 Key takeaways: - [ ] Robots.txt allows crawling of important pages - [ ] No accidental noindex tags on important pages - [ ] Unique title tag per page (50-60 chars) - [ ] HTTPS everywhere (no mixed content) - [ ] Core Web Vitals pass (LCP < 2.5s, INP < 200ms, CLS < 0.1) ## Crawlability - [ ] Robots.txt allows crawling of important pages - [ ] XML sitemap exists, is valid, and references only indexable URLs - [ ] No excessive crawl depth (important pages within 3 clicks) - [ ] No orphan pages (every page has at least one internal link) - [ ] Server responds within 200ms (TTFB) ## Indexability - [ ] No accidental noindex tags on important pages - [ ] Canonical tags present and correct on all pages - [ ] No duplicate titles or descriptions - [ ] Pagination uses self-referencing canonicals - [ ] Faceted navigation does not create combinatorial URL explosion ## On-Page SEO - [ ] Unique title tag per page (50-60 chars) - [ ] Meta description per page (150-160 chars) - [ ] Single H1 per page containing primary keyword - [ ] Logical heading hierarchy (H1 > H2 > H3) - [ ] Image alt text on all meaningful images - [ ] Internal links with descriptive anchor text ## Technical Infrastructure - [ ] HTTPS everywhere (no mixed content) - [ ] Proper 301 redirects (no chains or loops) - [ ] Custom 404 page with navigation - [ ] Hreflang tags for multilingual content - [ ] Structured data validates without errors ## Performance - [ ] Core Web Vitals pass (LCP < 2.5s, INP < 200ms, CLS < 0.1) - [ ] Gzip or Brotli compression enabled - [ ] Static assets cached with long max-age - [ ] Images optimized and served in next-gen formats ## Tools for Auditing | Tool | Focus | |------|------| | Screaming Frog | Crawl analysis, broken links | | Google Search Console | Indexing issues, performance | | Lighthouse | Performance, accessibility | | Ahrefs/SEMrush | Backlinks, keyword rankings | ### URL Structure and Slug Optimization for SEO Clean, descriptive URLs improve click-through rates and help search engines understand page content. This guide covers slug creation rules, URL hierarchy, and migration strategies. - URL: https://peasyseo.com/guides/url-structure-slug-optimization/ - Category: Best Practice - Reading time: 1 min - Words: 234 ## URL Best Practices | Rule | Example | |------|--------| | Use hyphens, not underscores | `/web-design/` not `/web_design/` | | Lowercase only | `/about-us/` not `/About-Us/` | | Short and descriptive | `/tools/pdf-merge/` not `/tools/id/12345/` | | Include target keyword | `/guides/svg-optimization/` | | Avoid unnecessary parameters | `/products/shoes/` not `/products?cat=shoes` | ## URL Hierarchy URLs should reflect your site's content hierarchy: ``` https://example.com/ (homepage) https://example.com/tools/ (category) https://example.com/tools/pdf-merge/ (tool page) https://example.com/guides/ (category) https://example.com/guides/pdf-tips/ (guide page) ``` ## Slug Creation Rules 1. Remove stop words (a, the, is, and) unless they add meaning 2. Use the primary keyword 3. Keep under 5 words when possible 4. Remove special characters and accents 5. Make it human-readable and memorable ## URL Migration When changing URL structures: 1. Create a complete redirect map (old → new) 2. Implement 301 redirects for every old URL 3. Update internal links to point to new URLs 4. Update XML sitemap 5. Monitor Search Console for crawl errors 6. Keep redirects in place permanently ## Common Mistakes - Changing URLs without setting up redirects (causes 404s and lost rankings) - Including dates in evergreen content URLs (`/2024/seo-tips/` becomes stale) - Using IDs instead of slugs (`/post/12345/` tells users and search engines nothing) - Redirect chains (A → B → C) that waste crawl budget and lose link equity - Duplicate content from trailing slash inconsistency (pick one and redirect the other) ### SVG Optimization: Reducing File Size While Maintaining Quality SVG files from design tools often contain unnecessary metadata, redundant paths, and bloated markup. Proper optimization can reduce SVG file size by 50-80% without any visual difference. - URL: https://peasyseo.com/guides/svg-optimization-techniques/ - Category: Best Practice - Reading time: 2 min - Words: 348 Key takeaways: - Design tools like Figma, Illustrator, and Sketch export SVGs with editor metadata, unnecessary precision (coordinates with 15 decimal places), hidden layers, empty groups, and redundant styling. - Design tools embed proprietary data: Illustrator's `<i:pgf>` blocks, Sketch's `sketch:` namespace attributes, Figma's layer IDs. - Never remove `<title>`, `<desc>`, or `aria-label` attributes. - For consistent results, integrate SVG optimization into your build pipeline. - ### viewBox Attribute The `viewBox` attribute is essential for responsive scaling. ## Why SVGs Need Optimization Design tools like Figma, Illustrator, and Sketch export SVGs with editor metadata, unnecessary precision (coordinates with 15 decimal places), hidden layers, empty groups, and redundant styling. A 50 KB icon from Figma often compresses to under 5 KB after optimization. ## Key Optimization Techniques ### Remove Editor Metadata Design tools embed proprietary data: Illustrator's `<i:pgf>` blocks, Sketch's `sketch:` namespace attributes, Figma's layer IDs. This data is only useful for reimporting into the original tool and should be stripped for production. ### Reduce Coordinate Precision Path coordinates exported as `M 12.847362847 23.948573629` can usually be safely reduced to `M 12.85 23.95` with no visible difference. Reducing precision from 15 to 2 decimal places typically saves 20-30% of file size in path-heavy SVGs. ### Simplify Paths Complex paths with hundreds of control points can often be simplified with minimal visual impact. Path simplification reduces the number of curve segments while maintaining the overall shape. This is particularly effective for traced or auto-generated paths. ### Convert Shapes to Paths Elements like `<rect>`, `<circle>`, and `<ellipse>` are actually more compact than their path equivalents, so keep them as primitives when possible. However, if a `<rect>` has complex transforms applied, converting it to a pre-transformed `<path>` can be smaller. ### Merge Similar Styles Inline `style` attributes repeated across elements waste bytes. Consolidate repeated styles into a single `<style>` block with CSS classes, or better yet, use `fill` and `stroke` attributes directly on parent `<g>` elements. ## What Not to Optimize ### Accessibility Attributes Never remove `<title>`, `<desc>`, or `aria-label` attributes. These provide screen reader access and should be added if missing, not removed. ### viewBox Attribute The `viewBox` attribute is essential for responsive scaling. Removing it forces the SVG to display at a fixed size. Always keep `viewBox` and remove … ### Image SEO: Alt Text, Filenames, and Compression Images generate significant search traffic through Google Images and enhance page relevance signals. Optimizing alt text, filenames, and compression improves both accessibility and rankings. - URL: https://peasyseo.com/guides/image-seo-alt-text-filenames/ - Category: How-To - Reading time: 1 min - Words: 283 Key takeaways: - Google Images drives approximately 22% of all web searches. - Alt text serves two purposes: it describes the image for visually impaired users (accessibility) and provides context for search engines. - Search engines use filenames as a relevance signal. - Use `srcset` and `sizes` attributes to serve appropriately sized images for each device: - Add `loading="lazy"` to below-the-fold images. ## Why Image SEO Matters Google Images drives approximately 22% of all web searches. Properly optimized images also enhance the page's topical relevance, improving organic rankings for the page itself. ## Alt Text Best Practices Alt text serves two purposes: it describes the image for visually impaired users (accessibility) and provides context for search engines. | Do | Don't | |----|------| | Describe the image accurately | Start with 'image of' or 'photo of' | | Include relevant keywords naturally | Stuff keywords unnaturally | | Keep under 125 characters | Leave alt text empty on informative images | | Leave decorative images alt="" | Add alt text to purely decorative images | **Good example**: `alt="Golden retriever puppy playing fetch in a park"` **Bad example**: `alt="dog puppy pet animal cute buy dog food cheap"` ## Filename Optimization Search engines use filenames as a relevance signal. Before uploading: - Use descriptive names: `golden-retriever-puppy.webp` not `IMG_4523.jpg` - Separate words with hyphens - Use lowercase letters only - Include the primary keyword ## Compression and Format | Format | Best For | Compression | |--------|----------|------------| | WebP | Photos and illustrations | 25-34% smaller than JPEG | | AVIF | High-quality photos | 30-50% smaller than JPEG | | SVG | Icons and logos | Infinitely scalable | | PNG | Screenshots with text | Lossless, larger files | ## Responsive Images Use `srcset` and `sizes` attributes to serve appropriately sized images for each device: ```html <img src="photo-800.webp" srcset="photo-400.webp 400w, photo-800.webp 800w, photo-1200.webp 1200w" sizes="(max-width: 600px) 400px, 800px" alt="Descriptive alt text"> ``` ## Lazy Loading Add `loading="lazy"` to below-the-fold images. Never lazy-load the LCP image (usually the hero image) as it delays the largest contentful paint. ### Video Metadata and EXIF Data: What Your Files Contain Video files embed metadata about creation date, camera settings, GPS location, and encoding parameters. Understanding this data helps with organization, privacy, and troubleshooting. - URL: https://peasyseo.com/guides/video-metadata-exif-data-explained/ - Category: How-To - Reading time: 1 min - Words: 223 Key takeaways: - Stored in the file container (MP4, MOV, MKV). - Videos from smartphones contain GPS coordinates by default. - Phone videos often have a rotation tag (0, 90, 180, 270 degrees) instead of physically rotated pixels. - Critical for format compatibility troubleshooting. ## Types of Video Metadata ### Container Metadata Stored in the file container (MP4, MOV, MKV). Includes title, artist, creation date, and chapter markers. This is what media players and file managers display. ### Stream Metadata Technical properties of video/audio streams: codec, bitrate, resolution, frame rate, color space, and sample rate. Critical for format compatibility troubleshooting. ### EXIF Data Camera-specific metadata embedded during recording. Includes GPS coordinates, camera model, lens info, exposure settings, and orientation. ## Privacy Concerns Videos from smartphones contain GPS coordinates by default. Before sharing publicly: - Strip GPS metadata using a metadata editor - Check for embedded thumbnails (may show original uncropped frame) - Remove creation timestamps if timing is sensitive - Social platforms strip most metadata on upload, but direct file sharing does not ## Useful Metadata Fields | Field | Location | Use | |-------|----------|-----| | Duration | Container | Display/organization | | Resolution | Stream | Compatibility check | | Codec | Stream | Playback troubleshooting | | GPS | EXIF | Location tagging | | Creation Date | Container/EXIF | Sorting/archiving | | Rotation | Container | Orientation correction | ## Rotation Tag Phone videos often have a rotation tag (0, 90, 180, 270 degrees) instead of physically rotated pixels. Some players ignore this tag, causing sideways playback. Re-encoding with physical rotation fixes this permanently. ### Redirect Chain Cleanup: Fixing Common Redirect Issues Redirect chains waste crawl budget, slow page loads, and leak link equity. This troubleshooting guide helps you identify and fix redirect issues that silently harm your SEO. - URL: https://peasyseo.com/guides/redirect-chain-cleanup-guide/ - Category: Troubleshooting - Reading time: 2 min - Words: 308 Key takeaways: - A redirect chain occurs when URL A redirects to B, which redirects to C (or further). - A loop occurs when URL A redirects to B, which redirects back to A. - Screaming Frog or Sitebulb will identify all redirect chains and loops. - Maintain a redirect map in your repository ## Types of Redirects | Code | Type | SEO Impact | |------|------|------------| | 301 | Permanent | Passes ~95% link equity | | 302 | Temporary | May not pass link equity | | 307 | Temporary (HTTP/1.1) | Preserves request method | | 308 | Permanent (HTTP/1.1) | Preserves request method | | Meta refresh | HTML-based | Poor UX, avoid | | JavaScript redirect | Client-side | Not always followed by crawlers | ## Redirect Chains A redirect chain occurs when URL A redirects to B, which redirects to C (or further). Each hop adds latency (~100-300ms per redirect) and may lose link equity. ``` Chain: /old-page → /renamed-page → /final-page Fix: /old-page → /final-page (direct) /renamed-page → /final-page (direct) ``` ## Redirect Loops A loop occurs when URL A redirects to B, which redirects back to A. The browser gives up after a few iterations (ERR_TOO_MANY_REDIRECTS). Common causes include conflicting server rules and CMS settings fighting each other. ## Finding Issues ### Using a Crawler Screaming Frog or Sitebulb will identify all redirect chains and loops. Filter by 'redirect chain' and 'redirect loop' reports. ### Search Console Check the Coverage report for 'redirect error' and 'page with redirect' statuses. ## Fixing Common Patterns | Pattern | Fix | |---------|----| | HTTP → HTTPS → www → non-www | Single redirect: HTTP www → HTTPS non-www | | Old slug → new slug → newer slug | All old versions → final URL | | 302 on permanent URL change | Change to 301 | | Trailing slash inconsistency | Pick one, redirect the other | ## Prevention - Maintain a redirect map in your repository - Audit redirects quarterly - When adding a redirect, check if the source URL already has inbound redirects pointing to it … ### SEO-Friendly JavaScript Rendering: CSR, SSR, and SSG Compared Search engines can render JavaScript, but not as reliably as plain HTML. Choosing the right rendering strategy ensures your content is discoverable and indexable without sacrificing interactivity. - URL: https://peasyseo.com/guides/seo-friendly-javascript-rendering/ - Category: Comparison - Reading time: 2 min - Words: 331 Key takeaways: - Google uses a two-phase indexing process: - Lazy-loaded content triggered by scroll events may not be rendered (Googlebot does not scroll) - Implement server-side rendering or pre-rendering for SEO-critical pages - Use Google Search Console URL Inspection to see how Googlebot renders your page ## Rendering Strategies | Strategy | How It Works | SEO Impact | |----------|-------------|------------| | CSR (Client-Side Rendering) | Browser downloads JS, renders content | Poor — Googlebot may not execute JS correctly | | SSR (Server-Side Rendering) | Server sends fully rendered HTML | Good — content is immediately available | | SSG (Static Site Generation) | HTML pre-built at build time | Best — fastest TTFB, no server rendering | | ISR (Incremental Static Regeneration) | SSG with on-demand revalidation | Good — combines SSG speed with dynamic content | ## How Googlebot Handles JavaScript Google uses a two-phase indexing process: 1. **Crawl phase**: Downloads HTML (no JS execution) 2. **Render phase**: Queues the page for rendering in a headless Chromium instance The render queue can introduce delays of seconds to days. Content that depends on JS rendering may not be indexed promptly. ## Known JS Rendering Issues - Lazy-loaded content triggered by scroll events may not be rendered (Googlebot does not scroll) - Client-side routing may not be properly crawled if links are not standard `<a href>` elements - Dynamic meta tags set via JavaScript may be missed in the initial crawl phase - Infinite scroll without pagination URLs creates content that Google cannot discover ## Best Practices for JS-Heavy Sites ### If Using CSR (React SPA, Vue SPA) - Implement server-side rendering or pre-rendering for SEO-critical pages - Use dynamic rendering (serve pre-rendered HTML to bots) as a temporary solution - Ensure all internal links use standard `<a>` tags with `href` attributes ### If Using SSR (Next.js, Nuxt) - Verify that initial HTML contains all critical content (view source, not inspect element) - Set proper meta tags server-side - Implement streaming SSR for faster TTFB ## Testing - Use Google Search Console URL Inspection to see … ### Image Accessibility: Writing Effective Alt Text Alt text makes images accessible to screen reader users and appears when images fail to load. It also contributes to image SEO. Writing useful alt text requires understanding context, purpose, and conciseness. - URL: https://peasyseo.com/guides/image-accessibility-alt-text-guide/ - Category: How-To - Reading time: 2 min - Words: 389 Key takeaways: - Approximately 2.2 billion people globally have a vision impairment. - Describe the function of the image, not just its appearance. - Images that convey information need descriptive alt text: - Keep alt text under 125 characters when possible. - Include relevant keywords naturally — alt text is a ranking signal for image search. ## Why Alt Text Matters Approximately 2.2 billion people globally have a vision impairment. Screen readers convert alt text to speech, making images accessible to blind and low-vision users. Beyond accessibility, alt text serves as fallback content when images fail to load (slow connections, CDN outages) and helps search engines understand image content for image search results. ## The Golden Rule Describe the **function** of the image, not just its appearance. Ask yourself: if I replaced this image with text, what would that text say? ## Writing Effective Alt Text ### Informational Images Images that convey information need descriptive alt text: - **Poor:** `alt="chart"` — provides no information - **Poor:** `alt="image of a bar chart showing quarterly revenue data for 2025 with Q1 at 2.3M Q2 at 2.8M..."` — too verbose - **Good:** `alt="Quarterly revenue chart — steady growth from $2.3M (Q1) to $3.1M (Q4) in 2025"` — conveys the key insight ### Decorative Images Images that serve only as visual decoration (background patterns, spacers, purely aesthetic photos) should have an empty alt attribute: `alt=""`. This tells screen readers to skip the image entirely. An image without an alt attribute at all is an accessibility error — the screen reader will read the filename instead. ### Functional Images Images used as buttons or links need alt text describing the action, not the image: - **Poor:** `alt="magnifying glass"` (on a search button) - **Good:** `alt="Search"` — describes what happens when clicked - **Poor:** `alt="red arrow pointing right"` (on a next-page button) - **Good:** `alt="Next page"` — describes the action ### Complex Images For complex images like infographics, charts, or diagrams, provide a brief alt text summarizing the key takeaway, then offer the full data in a text alternative nearby (a data table, expandable section, or linked page). ## Length Guidelines Keep … ## Glossary (49 terms) ### 301 Redirect (301 Permanent Redirect) An HTTP status code permanently redirecting one URL to another, transferring most link equity to the new URL. - URL: https://peasyseo.com/glossary/301-redirect/ ### Alt Text (Image Alternative Text) A text description of an image for accessibility and SEO, displayed when the image cannot be loaded. - URL: https://peasyseo.com/glossary/alt-text/ ### Anchor Text (Link Anchor Text) The visible clickable text of a hyperlink, providing context to search engines about the linked page's topic. - URL: https://peasyseo.com/glossary/anchor-text/ ### Backlink (Inbound Backlink) A hyperlink from one website to another, used by search engines as a signal of content authority and trust. - URL: https://peasyseo.com/glossary/backlink/ ### Breadcrumb (Breadcrumb Navigation) A hierarchical navigation trail showing the user's location within a site, enhancing UX and enabling rich results. - URL: https://peasyseo.com/glossary/breadcrumb/ ### Canonical URL (Canonical URL Tag) An HTML element specifying the preferred version of a page when duplicate or similar content exists at multiple URLs. - URL: https://peasyseo.com/glossary/canonical-url/ ### CLS (Cumulative Layout Shift) A Core Web Vital measuring unexpected layout movement during page load (target: under 0.1). - URL: https://peasyseo.com/glossary/cls/ ### Core Update (Google Core Algorithm Update) A broad change to Google's ranking algorithm affecting search results globally, often shifting traffic significantly. - URL: https://peasyseo.com/glossary/core-update/ ### Core Web Vitals (Core Web Vitals) Google's set of user experience metrics: LCP (loading), INP (interactivity), and CLS (visual stability). - URL: https://peasyseo.com/glossary/core-web-vitals/ ### Crawl Budget (Search Engine Crawl Budget) The number of pages a search engine will crawl on a site within a given time period. - URL: https://peasyseo.com/glossary/crawl-budget/ ### Domain Authority (Domain Authority Score) A search engine ranking score predicting how likely a website is to rank in search results, based on backlink profile and domain age. - URL: https://peasyseo.com/glossary/domain-authority/ ### Duplicate Content (Duplicate Content Issue) Substantially identical content appearing at multiple URLs, which can dilute search rankings and cause indexing confusion. - URL: https://peasyseo.com/glossary/duplicate-content/ ### Edge SEO (Edge SEO) Implementing SEO changes at the CDN or edge layer (e.g. Cloudflare Workers) without modifying the origin server. - URL: https://peasyseo.com/glossary/edge-seo/ ### E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) Google's quality rater guidelines criteria for evaluating content quality, especially important for YMYL topics. - URL: https://peasyseo.com/glossary/e-e-a-t/ ### Entity SEO (Entity-Based SEO) An optimization strategy focused on establishing entities and their relationships in Google's Knowledge Graph. - URL: https://peasyseo.com/glossary/entity-seo/ ### Featured Snippet (Google Featured Snippet) A highlighted excerpt from a web page displayed at the top of Google search results, answering the query directly. - URL: https://peasyseo.com/glossary/featured-snippet/ ### Helpful Content (Helpful Content System) A Google ranking system rewarding people-first content and demoting content written primarily for search engines. - URL: https://peasyseo.com/glossary/helpful-content/ ### Hreflang (Hreflang Attribute) An HTML attribute telling search engines which language and region a page targets, preventing duplicate content across locales. - URL: https://peasyseo.com/glossary/hreflang/ ### IndexNow (IndexNow Protocol) A protocol allowing websites to instantly notify search engines about content changes for faster indexing. - URL: https://peasyseo.com/glossary/indexnow/ ### INP (Interaction to Next Paint) A Core Web Vital measuring the latency of user interactions (clicks, taps) until the next visual update (target: under 200ms). - URL: https://peasyseo.com/glossary/inp/ ### Internal Linking (Internal Link Structure) Hyperlinks connecting pages within the same website, distributing link equity and helping crawlers discover content. - URL: https://peasyseo.com/glossary/internal-linking/ ### JSON-LD (JSON for Linking Data) A format for embedding structured data in web pages using JSON within a script tag, preferred by Google. - URL: https://peasyseo.com/glossary/json-ld/ ### Keyword Density (Keyword Density) The percentage of times a keyword appears in text relative to the total word count, used to avoid keyword stuffing. - URL: https://peasyseo.com/glossary/keyword-density/ ### Knowledge Graph (Google Knowledge Graph) Google's knowledge base that connects entities and facts to enhance search results with panels, carousels, and direct answers. - URL: https://peasyseo.com/glossary/knowledge-graph/ ### Knowledge Panel (Google Knowledge Panel) An information box appearing in Google search results, displaying key facts about a recognized entity. - URL: https://peasyseo.com/glossary/knowledge-panel/ ### LCP (Largest Contentful Paint) A Core Web Vital measuring the time until the largest visible content element is fully rendered (target: under 2.5s). - URL: https://peasyseo.com/glossary/lcp/ ### Local Pack (Google Local Pack) A SERP feature showing three local business results with a map, triggered by location-based search queries. - URL: https://peasyseo.com/glossary/local-pack/ ### Log File Analysis (SEO Log File Analysis) Examining server access logs to understand how search engine crawlers interact with a site's pages. - URL: https://peasyseo.com/glossary/log-file-analysis/ ### Long-Tail Keyword (Long-Tail Keyword) A specific, multi-word search query with lower volume but higher conversion intent, such as 'convert PNG to PDF online free'. - URL: https://peasyseo.com/glossary/long-tail-keyword/ ### Meta Description (Meta Description Tag) An HTML meta tag providing a brief summary of a page's content, often displayed in search engine results. - URL: https://peasyseo.com/glossary/meta-description/ ### Nofollow (Nofollow Link Attribute) An HTML attribute (rel='nofollow') that tells search engines not to pass ranking credit through a hyperlink. - URL: https://peasyseo.com/glossary/nofollow/ ### Noindex (Robots Noindex Directive) A meta tag or HTTP header instructing search engines not to include a page in their search index. - URL: https://peasyseo.com/glossary/noindex/ ### Open Graph (Open Graph Protocol) A set of meta tags controlling how pages appear when shared on social media (title, description, image). - URL: https://peasyseo.com/glossary/open-graph/ ### Orphan Page (Orphan Page (SEO)) A web page with no internal links pointing to it, making it difficult for search engine crawlers and users to discover. - URL: https://peasyseo.com/glossary/orphan-page/ ### Page Experience (Google Page Experience Signal) A ranking signal combining Core Web Vitals, mobile-friendliness, HTTPS, and no intrusive interstitials. - URL: https://peasyseo.com/glossary/page-experience/ ### Pagination SEO (SEO Pagination Best Practices) Techniques for helping search engines crawl paginated content, including rel=next/prev, load-more patterns, and view-all pages. - URL: https://peasyseo.com/glossary/pagination-seo/ ### Passage Ranking (Google Passage Ranking) A Google feature that indexes and ranks individual passages within a page, allowing specific sections to appear in search results. - URL: https://peasyseo.com/glossary/passage-ranking/ ### People Also Ask (People Also Ask (PAA)) An expandable section in Google results showing related questions, each linking to a featured snippet from a different page. - URL: https://peasyseo.com/glossary/people-also-ask/ ### Rendering Budget (Search Engine Rendering Budget) The computational resources a search engine allocates to render JavaScript-dependent pages for indexing. - URL: https://peasyseo.com/glossary/rendering-budget/ ### Rich Snippet (Rich Search Result Snippet) Enhanced search results displaying additional information (ratings, prices, FAQs) extracted from structured data. - URL: https://peasyseo.com/glossary/rich-snippet/ ### Robots.txt (Robots Exclusion Protocol) A text file at the site root instructing search engine crawlers which pages or directories to avoid. - URL: https://peasyseo.com/glossary/robotstxt/ ### Schema Markup (Schema.org Structured Data) A vocabulary of tags added to HTML to help search engines understand page content and display rich results. - URL: https://peasyseo.com/glossary/schema-markup/ ### Search Intent (User Search Intent) The underlying goal behind a search query — informational, navigational, transactional, or commercial — guiding content strategy. - URL: https://peasyseo.com/glossary/search-intent/ ### SERP (Search Engine Results Page) The page displayed by a search engine in response to a query, containing organic results, ads, and featured snippets. - URL: https://peasyseo.com/glossary/serp/ ### Sitemap XML (XML Sitemap) An XML file listing all important URLs on a site, helping search engines discover and index content efficiently. - URL: https://peasyseo.com/glossary/sitemap-xml/ ### Title Tag (HTML Title Tag) The HTML element defining the title of a web page, displayed in browser tabs and search engine results. - URL: https://peasyseo.com/glossary/title-tag/ ### Topical Authority (Topical Authority) A site's perceived expertise on a subject, built by creating comprehensive, interlinked content covering all aspects of a topic. - URL: https://peasyseo.com/glossary/topical-authority/ ### TTFB (Time to First Byte) The time between a browser's HTTP request and receiving the first byte of the response, measuring server responsiveness. - URL: https://peasyseo.com/glossary/ttfb/ ### YMYL (Your Money or Your Life) Google's classification for pages that could impact a user's health, finances, or safety, held to the highest quality standards. - URL: https://peasyseo.com/glossary/ymyl/ ## API Base URL: https://peasyseo.com/api/v1/ | Endpoint | Description | |----------|-------------| | GET /api/v1/tools/ | List all tools (filterable by category) | | GET /api/v1/tools/{slug}/ | Tool detail with description, steps, FAQ | | GET /api/v1/categories/ | Tool categories | | GET /api/v1/formats/ | File formats reference | | GET /api/v1/formats/{slug}/ | Format detail with history, pros/cons | | GET /api/v1/conversions/ | Format conversion guides | | GET /api/v1/glossary/ | Terminology with definitions | | GET /api/v1/glossary/{slug}/ | Term with simple + technical explanations, code examples, references | | GET /api/v1/guides/ | Educational guides (filterable by category, audience_level) | | GET /api/v1/guides/{slug}/ | Full guide with content, takeaways, ToC, related guides | | GET /api/v1/use-cases/ | Real-world use cases by industry | | GET /api/v1/search/?q={query} | Cross-model search | | GET /api/v1/sites/ | All 16 Peasy sites | OpenAPI spec: https://peasyseo.com/api/openapi.json ## Content Negotiation All pages support Markdown output for AI agents: - Add `?format=md` to any page URL - Or send `Accept: text/markdown` header ## Platform Stats - 251 tools across 16 sites - 131 file formats documented - 1484 format conversion guides - 695 glossary terms (with simple + technical explanations) - 645 educational guides (avg 1,308 words) - 302 real-world use cases