# Allow all bots
User-agent: *
Allow: /

# Block admin & private areas
Disallow: /admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Disallow: /wp-admin/
Disallow: /wp-includes/

# Block search & filter pages (duplicate content)
Disallow: /*?s=
Disallow: /*?sort=
Disallow: /*?filter=

# Block unnecessary file types
Disallow: /*.pdf$
Disallow: /*.doc$

# Allow CSS & JS (important for rendering)
Allow: /wp-content/uploads/
Allow: /*.css$
Allow: /*.js$

# Sitemap location
Sitemap: https://example.com/sitemap.xml
Sitemap: https://example.com/sitemap-news.xml

Disallow: /blog/  # Blocks entire blog - BAD!

Disallow: /*.css$  # Google can't render page properly
Disallow: /*.js$

# Missing sitemap = harder for Google to discover URLs

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/post-sitemap.xml</loc>
    <lastmod>2025-12-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/page-sitemap.xml</loc>
    <lastmod>2025-12-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/product-sitemap.xml</loc>
    <lastmod>2025-12-15</lastmod>
  </sitemap>
</sitemapindex>

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/article-slug/</loc>
    <lastmod>2025-12-15</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://example.com/another-article/</loc>
    <lastmod>2025-12-10</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
</urlset>

# In robots.txt (only if server overload)
User-agent: *
Crawl-delay: 10

example.com/tshirt?color=red
example.com/tshirt?color=blue
example.com/tshirt?color=green

→ All should canonical to:
example.com/tshirt

example.com/blog/page/1/
example.com/blog/page/2/

→ Use rel="next" and rel="prev" OR
→ Self-referencing canonical

http://example.com/page/
https://example.com/page/

→ HTTP version canonicals to HTTPS

<link rel="canonical" href="https://example.com/original-page/" />

<!-- Don't index this page, but follow links -->
<meta name="robots" content="noindex, follow" />

<!-- Don't index, don't follow links -->
<meta name="robots" content="noindex, nofollow" />

<!-- Index page, don't follow links -->
<meta name="robots" content="index, nofollow" />

X-Robots-Tag: noindex, nofollow

✅ example.com/seo-guide/
✅ example.com/blog/technical-seo/
✅ example.com/products/laptop-gaming/

❌ example.com/p?id=12345
❌ example.com/2025/12/15/post-title-with-unnecessary-date/
❌ example.com/category/subcategory/sub-subcategory/product/
❌ example.com/page.php?session=abc123&ref=xyz

Homepage (Level 0)
├─ Category 1 (Level 1)
│   ├─ Subcategory 1a (Level 2)
│   │   ├─ Product/Article 1 (Level 3)
│   │   └─ Product/Article 2 (Level 3)
│   └─ Subcategory 1b (Level 2)
│       └─ Product/Article 3 (Level 3)
├─ Category 2 (Level 1)
│   └─ Product/Article 4 (Level 2)
└─ Category 3 (Level 1)
    └─ Product/Article 5 (Level 2)

<nav aria-label="Breadcrumb">
  <ol itemscope itemtype="https://schema.org/BreadcrumbList">
    <li
      itemprop="itemListElement"
      itemscope
      itemtype="https://schema.org/ListItem"
    >
      <a itemprop="item" href="https://example.com/">
        <span itemprop="name">Home</span>
      </a>
      <meta itemprop="position" content="1" />
    </li>
    <li
      itemprop="itemListElement"
      itemscope
      itemtype="https://schema.org/ListItem"
    >
      <a itemprop="item" href="https://example.com/seo/">
        <span itemprop="name">SEO</span>
      </a>
      <meta itemprop="position" content="2" />
    </li>
    <li
      itemprop="itemListElement"
      itemscope
      itemtype="https://schema.org/ListItem"
    >
      <a itemprop="item" href="https://example.com/seo/technical-seo/">
        <span itemprop="name">Technical SEO</span>
      </a>
      <meta itemprop="position" content="3" />
    </li>
  </ol>
</nav>

<!-- On /blog/page/2/ -->
<link rel="canonical" href="https://example.com/blog/page/2/" />

<link rel="canonical" href="https://example.com/blog/all/" />

<!-- On page 2 -->
<link rel="prev" href="https://example.com/blog/page/1/" />
<link rel="next" href="https://example.com/blog/page/3/" />

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

server {
    listen 80;
    server_name example.com www.example.com;
    return 301 https://$server_name$request_uri;
}

# HSTS (HTTP Strict Transport Security)
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;

# X-Frame-Options (prevent clickjacking)
add_header X-Frame-Options "SAMEORIGIN" always;

# X-Content-Type-Options
add_header X-Content-Type-Options "nosniff" always;

# X-XSS-Protection
add_header X-XSS-Protection "1; mode=block" always;

# Referrer Policy
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

<meta name="viewport" content="width=device-width, initial-scale=1.0" />

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Technical SEO Panduan Lengkap",
  "image": ["https://example.com/image.jpg"],
  "datePublished": "2025-12-15T14:00:00+00:00",
  "dateModified": "2025-12-15T14:00:00+00:00",
  "author": {
    "@type": "Person",
    "name": "John Doe",
    "url": "https://example.com/author/john/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "SEO Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.jpg"
    }
  },
  "description": "Panduan komprehensif Technical SEO..."
}

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Apa itu Technical SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Technical SEO adalah praktik optimasi aspek teknis website agar search engine bisa crawl, index, dan understand konten dengan efisien."
      }
    },
    {
      "@type": "Question",
      "name": "Mengapa Technical SEO penting?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Technical SEO adalah fondasi yang menentukan apakah Google bisa crawl dan index website Anda. Tanpa technical SEO yang baik, konten berkualitas tidak akan ranking optimal."
      }
    }
  ]
}

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Laptop Gaming XYZ",
  "image": "https://example.com/laptop.jpg",
  "description": "High-performance gaming laptop...",
  "sku": "LAP123",
  "brand": {
    "@type": "Brand",
    "name": "BrandName"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/laptop-xyz/",
    "priceCurrency": "IDR",
    "price": "15000000",
    "availability": "https://schema.org/InStock",
    "seller": {
      "@type": "Organization",
      "name": "Example Store"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.5",
    "reviewCount": "89"
  }
}

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Example Cafe",
  "image": "https://example.com/cafe.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Jl. Sudirman 123",
    "addressLocality": "Jakarta",
    "addressRegion": "DKI Jakarta",
    "postalCode": "12345",
    "addressCountry": "ID"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": -6.2088,
    "longitude": 106.8456
  },
  "telephone": "+62211234567",
  "priceRange": "$$",
  "servesCuisine": "Coffee, Breakfast",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "22:00"
    }
  ]
}

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    ...
  }
</script>

http://example.com
http://www.example.com
https://example.com
https://www.example.com

RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]

example.com/page
example.com/page/

example.com/product?color=red
example.com/product?color=blue
example.com/product?sort=price

example.com/article
example.com/article/print

<!-- English version -->
<link rel="alternate" hreflang="en" href="https://example.com/en/" />

<!-- Indonesian version -->
<link rel="alternate" hreflang="id" href="https://example.com/id/" />

<!-- English for US -->
<link rel="alternate" hreflang="en-us" href="https://example.com/us/" />

<!-- English for UK -->
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/" />

<!-- Default fallback -->
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

example.co.id (Indonesia)
example.com.sg (Singapore)
example.com.my (Malaysia)

id.example.com
sg.example.com

example.com/id/
example.com/sg/

// BAD: Blocking main thread
function processLargeData() {
  for (let i = 0; i < 1000000; i++) {
    // Heavy computation
  }
}

// GOOD: Break into chunks
async function processLargeDataChunked() {
  const chunkSize = 1000;
  for (let i = 0; i < 1000000; i += chunkSize) {
    await new Promise((resolve) => setTimeout(resolve, 0));
    // Process chunk
  }
}

// BAD: No debouncing
input.addEventListener("keyup", () => {
  expensiveSearch();
});

// GOOD: Debounced
input.addEventListener(
  "keyup",
  debounce(() => {
    expensiveSearch();
  }, 300)
);

<!-- Load non-critical scripts async -->
<script src="analytics.js" async></script>
<script src="chat-widget.js" defer></script>

<!-- Use Partytown for CPU-intensive third-party -->
<script type="text/partytown" src="heavy-library.js"></script>

✅ Code splitting (load only what's needed)
✅ Lazy load non-critical JavaScript
✅ Use Web Workers for heavy computations
✅ Debounce/throttle event handlers
✅ Minimize main thread work
✅ Use requestIdleCallback untuk non-urgent tasks
✅ Optimize event delegation
✅ Remove unused JavaScript (tree shaking)

// Web Vitals library
import { onINP } from "web-vitals";

onINP((metric) => {
  console.log("INP:", metric.value);
  // Send to analytics
  gtag("event", "web_vitals", {
    name: "INP",
    value: Math.round(metric.value),
    id: metric.id,
  });
});

# Nginx config
map $http_user_agent $is_bot {
  default 0;
  ~*(googlebot|bingbot|baiduspider) 1;
}

location / {
  if ($is_bot) {
    proxy_pass http://prerender_server;
  }
  # Regular traffic
}

<!-- Ensure meta tags in initial HTML, not JS-injected -->
<head>
  <title>Page Title - Not JS-Generated</title>
  <meta name="description" content="Static description" />
  <link rel="canonical" href="https://example.com/page/" />
</head>

<!-- Server-rendered skeleton -->
<div class="skeleton">
  <div class="skeleton-header"></div>
  <div class="skeleton-text"></div>
</div>

<!-- JavaScript hydrates with real content -->
<script>
  fetch("/api/content").then((data) => {
    // Replace skeleton
  });
</script>

# Google's URL Inspection Tool in GSC
# Shows exactly what Google renders

<!-- DNS prefetch untuk external domains -->
<link rel="dns-prefetch" href="//fonts.googleapis.com" />

<!-- Preconnect untuk critical origins -->
<link rel="preconnect" href="https://cdn.example.com" crossorigin />

<!-- Prefetch untuk next-page navigation -->
<link rel="prefetch" href="/next-page.html" />

<!-- Preload critical resources -->
<link rel="preload" as="image" href="hero.webp" fetchpriority="high" />
<link rel="preload" as="font" href="font.woff2" type="font/woff2" crossorigin />

<!-- Modern formats dengan fallback -->
<picture>
  <source
    srcset="image-320w.avif 320w, image-640w.avif 640w, image-1280w.avif 1280w"
    sizes="(max-width: 640px) 100vw, 640px"
    type="image/avif"
  />
  <source
    srcset="image-320w.webp 320w, image-640w.webp 640w, image-1280w.webp 1280w"
    sizes="(max-width: 640px) 100vw, 640px"
    type="image/webp"
  />
  <img
    src="image-640w.jpg"
    alt="Description"
    width="640"
    height="480"
    loading="lazy"
    decoding="async"
  />
</picture>

<head>
  <!-- Inline critical CSS (above-the-fold) -->
  <style>
    /* Critical CSS here */
    .header {
      /* ... */
    }
    .hero {
      /* ... */
    }
  </style>

  <!-- Load full CSS async -->
  <link
    rel="preload"
    href="styles.css"
    as="style"
    onload="this.onload=null;this.rel='stylesheet'"
  />
  <noscript><link rel="stylesheet" href="styles.css" /></noscript>
</head>

/* Ads, embeds, lazy-loaded images */
.ad-container {
  min-height: 250px; /* Reserve exact space */
  background: #f0f0f0;
}

/* Images dengan aspect-ratio */
img {
  aspect-ratio: attr(width) / attr(height); /* Future CSS */
  width: 100%;
  height: auto;
}

/* Current solution */
img {
  width: 100%;
  height: auto;
}

/* Option 1: font-display swap (flash of unstyled text OK) */
@font-face {
  font-family: 'CustomFont';
  src: url('font.woff2') format('woff2');
  font-display: swap;
}

/* Option 2: font-display optional (system font if slow) */
@font-face {
  font-family: 'CustomFont';
  src: url('font.woff2') format('woff2');
  font-display: optional;
}

/* Preload important fonts */
<link rel="preload" href="font.woff2" as="font" type="font/woff2" crossorigin>

/* GOOD: Transform/opacity don't cause reflow */
.element {
  transition: transform 0.3s, opacity 0.3s;
}

.element:hover {
  transform: scale(1.1);
  opacity: 0.8;
}

/* BAD: Width/height/margin cause layout shift */
.element {
  transition: width 0.3s;
}

.element:hover {
  width: 200px; /* Causes reflow */
}

✅ Mobile has SAME content as desktop
✅ Structured data identical on both
✅ Meta tags sama di mobile dan desktop
✅ Images accessible on mobile
✅ Videos embedded properly on mobile

<!-- Viewport meta tag (wajib) -->
<meta name="viewport" content="width=device-width, initial-scale=1" />

<!-- Touch-friendly elements (min 48x48px) -->
<button style="min-width: 48px; min-height: 48px;">Click</button>

<!-- Readable fonts (min 16px base) -->
<body style="font-size: 16px;"></body>

Target Mobile Metrics:
- LCP: < 2.5s (on 4G)
- INP: < 200ms
- CLS: < 0.1
- FCP: < 1.8s
- TTFB: < 600ms

❌ Intrusive interstitials (popup yang block content)
❌ Flash content (not supported)
❌ Unplayable videos (wrong format)
❌ Tiny fonts (< 12px)
❌ Touch targets terlalu kecil (< 48px)
❌ Horizontal scrolling required

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is technical SEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Technical SEO is the practice of optimizing the technical aspects of a website to improve search engine crawling and indexing.</p>"
      }
    },
    {
      "@type": "Question",
      "name": "How often should I do technical SEO audit?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Perform technical SEO audits quarterly for most websites, or monthly for high-traffic sites with frequent updates.</p>"
      }
    }
  ]
}

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Fix 404 Errors",
  "description": "Step-by-step guide to identify and fix 404 errors",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Export 404 errors from Google Search Console",
      "text": "Navigate to Coverage report and filter by 404 errors",
      "image": "https://example.com/step1.jpg"
    },
    {
      "@type": "HowToStep",
      "name": "Decide: Redirect or Fix",
      "text": "If content moved, use 301 redirect. If deleted permanently, ensure 404 is served."
    }
  ],
  "totalTime": "PT30M"
}

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "SEO",
      "item": "https://example.com/seo/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Technical SEO",
      "item": "https://example.com/seo/technical-seo/"
    }
  ]
}

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "Technical SEO Tutorial",
  "description": "Complete technical SEO guide for beginners",
  "thumbnailUrl": "https://example.com/thumbnail.jpg",
  "uploadDate": "2026-12-17",
  "duration": "PT10M30S",
  "contentUrl": "https://example.com/video.mp4",
  "embedUrl": "https://youtube.com/embed/abc123"
}

1. Add schema to page (JSON-LD recommended)
2. Test with Google Rich Results Test
3. Deploy to production
4. Monitor in Search Console → Enhancements
5. Check for errors/warnings
6. Iterate and improve

<!-- Example: English, Indonesian, Spanish for different countries -->

<!-- English - Global default -->
<link rel="alternate" hreflang="en" href="https://example.com/en/" />

<!-- English - United States -->
<link rel="alternate" hreflang="en-us" href="https://example.com/en-us/" />

<!-- English - United Kingdom -->
<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb/" />

<!-- Indonesian - Indonesia -->
<link rel="alternate" hreflang="id-id" href="https://example.com/id/" />

<!-- Spanish - Spain -->
<link rel="alternate" hreflang="es-es" href="https://example.com/es/" />

<!-- Spanish - Mexico -->
<link rel="alternate" hreflang="es-mx" href="https://example.com/es-mx/" />

<!-- Default fallback (usually English or most popular) -->
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <url>
    <loc>https://example.com/en/page/</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/page/" />
    <xhtml:link rel="alternate" hreflang="id-id" href="https://example.com/id/page/" />
    <xhtml:link rel="alternate" hreflang="es-es" href="https://example.com/es/page/" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/page/" />
  </url>
  <url>
    <loc>https://example.com/id/page/</loc>
    <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/page/" />
    <xhtml:link rel="alternate" hreflang="id-id" href="https://example.com/id/page/" />
    <xhtml:link rel="alternate" hreflang="es-es" href="https://example.com/es/page/" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/page/" />
  </url>
</urlset>

❌ Missing return tags (A links to B, but B doesn't link back to A)
❌ Wrong language codes (using "in" instead of "id" for Indonesian)
❌ Mixing URL structures (some /id/, some id.example.com)
❌ No x-default specified
❌ Self-referencing hreflang missing
❌ Conflicting signals (hreflang says EN, html lang says ID)

# Nginx configuration
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
add_header X-Frame-Options "SAMEORIGIN" always;
add_header X-Content-Type-Options "nosniff" always;
add_header X-XSS-Protection "1; mode=block" always;
add_header Referrer-Policy "strict-origin-when-cross-origin" always;
add_header Permissions-Policy "geolocation=(), microphone=(), camera=()" always;

# Content Security Policy
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline' https://trusted-cdn.com; style-src 'self' 'unsafe-inline';" always;

<IfModule mod_headers.c>
  Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
  Header always set X-Frame-Options "SAMEORIGIN"
  Header always set X-Content-Type-Options "nosniff"
  Header always set X-XSS-Protection "1; mode=block"
  Header always set Referrer-Policy "strict-origin-when-cross-origin"
</IfModule>

IF blog/content site:
  → Focus 70% LCP, 30% INP

IF e-commerce/app:
  → Focus 50% LCP, 50% INP

IF web app/dashboard:
  → Focus 30% LCP, 70% INP

// Next.js (SSR)
export async function getServerSideProps() {
  const data = await fetchData();
  return { props: { data } };
}

// Next.js (SSG - even better)
export async function getStaticProps() {
  const data = await fetchData();
  return { props: { data } };
}

// Critical content SSR, interactive features CSR
<div>
  {/* Server-rendered content */}
  <h1>SEO-Critical Title</h1>
  <p>SEO-critical first paragraph...</p>

  {/* Client-side interactive widget */}
  <ClientOnlyWidget />
</div>

// Serve static HTML to bots, JS to users
if (isBot(userAgent)) {
  return prerenderService.render(url);
} else {
  return clientApp;
}

# Test exactly what Google sees
1. Google Search Console → URL Inspection
2. View "Crawled Page" → Screenshot
3. Compare with actual page
4. Fix any discrepancies

Google Search Console → Settings → Crawl Stats

Red flags:
- Total crawl requests flat/declining
- Many pages discovered but not indexed
- Long delay between publish → indexing
- Important pages not crawled recently

❌ Remove:
- Duplicate pages
- Low-value pages (tags, archives)
- Infinite scroll pages
- Faceted navigation pages
- Thank you/confirmation pages

User-agent: *
# Block low-value sections
Disallow: /admin/
Disallow: /search?*
Disallow: /*?sort=*
Disallow: /*?filter=*
Disallow: /cart/
Disallow: /checkout/

# Allow important sections
Allow: /products/
Allow: /blog/
Allow: /categories/

Critical pages (want frequent crawling):
  → 1-2 clicks dari homepage
  → Many internal links pointing to them
  → Featured in navigation/footer

Low-priority pages:
  → 3-4 clicks dari homepage
  → Minimal internal links
  → Canonical if duplicate

Fast server response (< 200ms) = Google crawls more pages/session
Slow server (> 1000ms) = Fewer pages crawled

<url>
  <loc>https://example.com/important-page/</loc>
  <priority>1.0</priority>
  <changefreq>daily</changefreq>
</url>

<url>
  <loc>https://example.com/less-important/</loc>
  <priority>0.3</priority>
  <changefreq>monthly</changefreq>
</url>

Scenario: Same content on 3 URLs
- URL A: /product?color=red
- URL B: /product?color=blue
- URL C: /product

Google shows ONLY 1 in search results (usually canonical version)
→ Other versions invisible, bukan penalty, just hidden

IF multiple versions indexed:
  → Backlinks split across URLs
  → Authority diluted
  → Lower rankings for all versions

IF canonical properly set:
  → Authority consolidated
  → One strong page ranks better

1000 pages × 3 duplicate versions each = 3,000 total pages
→ Google wastes budget crawling duplicates
→ Less budget for unique pages
→ Slower indexing for new content

<!-- On duplicate pages -->
<link rel="canonical" href="https://example.com/original/" />

# Redirect duplicates to canonical
location /duplicate-page {
  return 301 https://example.com/original/;
}

<meta name="robots" content="noindex, follow" />

Google Search Console → URL Parameters
Configure how Google treats parameters

IF you copy content from other sites:
  → THAT can cause penalty
  → Manual action possible
  → Rankings tank

IF others copy YOUR content:
  → Usually not your problem
  → Google identifies original source
  → File DMCA if needed

Slow server di target country (500ms TTFB)
  WORSE than
Fast CDN globally (100ms TTFB)

Origin server: Singapore
CDN nodes: 200+ locations globally

User di Indonesia → served from Jakarta node (10ms)
User di USA → served from New York node (15ms)
User di Europe → served from Frankfurt node (12ms)

→ Server location irrelevant dengan CDN

.id = Indonesia (strongest)
.sg = Singapore
.com.my = Malaysia

.com hosted in Indonesia + GSC geo-target = Good

.com with global CDN = No specific country preference
→ Must use GSC country targeting

Option 1: ccTLD + Local Hosting + CDN
example.id + IDC Jakarta + Cloudflare
= Strongest local SEO signal

Option 2: gTLD + CDN + GSC Targeting
example.com + Cloudflare + GSC set to Indonesia
= Good balance global + local

Option 1: Subdomains + CDN
id.example.com (Indonesia)
sg.example.com (Singapore)
+ Global CDN

Option 2: Subdirectories + CDN + Hreflang
example.com/id/ (Indonesia)
example.com/sg/ (Singapore)
+ Hreflang tags
+ Global CDN

Target TTFB (Time to First Byte):
- < 200ms: Excellent
- 200-500ms: Good
- 500-1000ms: Acceptable
- > 1000ms: Problem (affects LCP, rankings)

# Test TTFB globally
Tools:
- GTmetrix (select test location)
- WebPageTest (multiple locations)
- Pingdom (multiple locations)
- KeyCDN Performance Test

Expected: < 200ms TTFB dari target regions

✅ E-commerce (payment processing)
✅ Login/signup pages
✅ YMYL sites (medical, financial, legal)
✅ Sites collecting any user data

✅ All business websites
✅ Blogs with comments/subscriptions
✅ Sites with contact forms

1. [ ] Purchase/renew SSL certificate
   - Let's Encrypt (free, recommended)
   - Commercial SSL (paid, support included)

2. [ ] Backup website completely

3. [ ] List all HTTP URLs needing redirects

4. [ ] Test SSL installation (SSL Labs Test)

5. [ ] Install SSL certificate on server

6. [ ] Implement 301 redirects (HTTP → HTTPS)
   Apache:
   RewriteEngine On
   RewriteCond %{HTTPS} off
   RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [L,R=301]

   Nginx:
   server {
     listen 80;
     return 301 https://$host$request_uri;
   }

7. [ ] Update internal links to HTTPS

8. [ ] Update canonical tags to HTTPS

9. [ ] Update XML sitemap URLs to HTTPS

10. [ ] Implement HSTS header
    Strict-Transport-Security: max-age=31536000

11. [ ] Add HTTPS property to Google Search Console

12. [ ] Submit HTTPS sitemap

13. [ ] Update robots.txt sitemap reference

14. [ ] Check for mixed content warnings
    (Chrome DevTools Console)

15. [ ] Update social media links

16. [ ] Update Google Analytics property

17. [ ] Monitor traffic for 7-14 days

18. [ ] Check rankings stability

<!-- HTTPS page loading HTTP resources -->
❌ <img src="http://example.com/image.jpg" /> ✅
<img src="https://example.com/image.jpg" />

❌
<script src="http://cdn.com/script.js"></script>
✅
<script src="https://cdn.com/script.js"></script>

- Expired certificate → Renew immediately
- Self-signed → Get proper certificate
- Name mismatch → Certificate must match domain
- Mixed intermediates → Proper certificate chain

HTTPS adds ~50-200ms overhead (TLS handshake)

Mitigation:
- HTTP/2 (multiplexing reduces overhead)
- TLS 1.3 (faster handshake)
- Session resumption
- CDN with optimized TLS

Time: 15-30 minutes
Focus:
- GSC errors (new issues)
- Crawl stats trends
- Core Web Vitals scores
- Server uptime
- Major broken links

Time: 2-4 hours
Checklist:
- Full site crawl (Screaming Frog)
- Index coverage report
- Core Web Vitals detailed analysis
- Structured data errors
- Mobile usability issues
- Security issues
- Duplicate content check
- Canonical tags review
- Internal linking analysis
- XML sitemap validation

Time: 8-16 hours
Deep dive:
- Complete crawl analysis
- Log file analysis
- Backlink profile audit
- Competitor technical comparison
- Site architecture review
- Page speed optimization
- Schema markup expansion
- International SEO (if applicable)
- Accessibility audit
- Security headers review

⚠️ Traffic drop > 20%
⚠️ Rankings drop significantly
⚠️ Google algorithm update
⚠️ Site redesign/migration
⚠️ Platform change (WordPress → Shopify)
⚠️ Manual action received
⚠️ Core Web Vitals failing
⚠️ Mass deindexing (pages dropping from index)