[{"data":1,"prerenderedAt":1478},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites":3,"all-docs-nav":936},{"id":4,"title":5,"body":6,"breadcrumb":912,"dateModified":922,"datePublished":922,"description":923,"extension":924,"faq":925,"meta":930,"navigation":131,"path":931,"seo":932,"slug":12,"stem":933,"type":934,"__hash__":935},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites\u002Findex.md","Netlify Redirects and Rewrites for Static Sites",{"type":7,"value":8,"toc":892},"minimark",[9,13,22,31,36,52,56,77,87,162,170,339,343,373,376,380,395,401,415,419,426,433,439,445,460,464,467,494,600,617,621,624,630,633,723,727,742,746,752,756,803,807,813,817,822,825,829,832,836,839,843,846,850,888],[10,11,5],"h1",{"id":12},"netlify-redirects-and-rewrites-for-static-sites",[14,15,16,17,21],"p",{},"Netlify's redirect engine is one of its most useful features for static sites, and one of the easiest to misconfigure. The same syntax handles permanent moves after a migration, clean URLs for single-page apps, proxying an API to avoid CORS, and sending German-speaking visitors to ",[18,19,20],"code",{},"\u002Fde\u002F",". The rules look simple, but ordering, shadowing and the difference between redirects and rewrites catch almost everyone at least once.",[14,23,24,25,30],{},"This guide covers both configuration files, status codes and when each applies, splats and placeholders, the shadowing rule that makes redirects \"not work\", proxy rewrites, and conditions for country and language. It is part of ",[26,27,29],"a",{"href":28},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002F","Netlify vs Vercel Deployment Strategies",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,46],"ul",{},[40,41,42],"li",{},"A static site deployed on Netlify.",[40,44,45],{},"A list of the redirects you need, with old and new paths.",[40,47,48,49,30],{},"The Netlify CLI for local testing: ",[18,50,51],{},"npm install -D netlify-cli",[32,53,55],{"id":54},"two-places-to-write-rules","Two Places to Write Rules",[14,57,58,59,62,63,66,67,70,71,73,74,76],{},"Rules can live in a ",[18,60,61],{},"_redirects"," file in the publish directory, or in ",[18,64,65],{},"[[redirects]]"," blocks in ",[18,68,69],{},"netlify.toml"," at the repository root. Netlify processes ",[18,72,61],{}," first, then ",[18,75,69],{},", and within each file the first matching rule wins.",[78,79,85],"pre",{"className":80,"code":82,"language":83,"meta":84},[81],"language-text","# _redirects\n\u002Fold-guide\u002F          \u002Fguides\u002Fnew-guide\u002F      301\n\u002Fblog\u002F*              \u002Farticles\u002F:splat        301\n\u002Fdocs\u002F:version\u002F*     \u002Fdocs\u002F:splat?v=:version 302\n\u002Fapi\u002F*               https:\u002F\u002Fapi.example.com\u002F:splat  200\n\u002F*                   \u002Findex.html             200\n","text","",[18,86,82],{"__ignoreMap":84},[78,88,92],{"className":89,"code":90,"language":91,"meta":84,"style":84},"language-toml shiki shiki-themes github-light github-dark","# netlify.toml\n[[redirects]]\n  from = \"\u002Fold-guide\u002F\"\n  to = \"\u002Fguides\u002Fnew-guide\u002F\"\n  status = 301\n\n[[redirects]]\n  from = \"\u002Fapi\u002F*\"\n  to = \"https:\u002F\u002Fapi.example.com\u002F:splat\"\n  status = 200\n  headers = { X-From = \"netlify\" }\n","toml",[18,93,94,102,108,114,120,126,133,138,144,150,156],{"__ignoreMap":84},[95,96,99],"span",{"class":97,"line":98},"line",1,[95,100,101],{},"# netlify.toml\n",[95,103,105],{"class":97,"line":104},2,[95,106,107],{},"[[redirects]]\n",[95,109,111],{"class":97,"line":110},3,[95,112,113],{},"  from = \"\u002Fold-guide\u002F\"\n",[95,115,117],{"class":97,"line":116},4,[95,118,119],{},"  to = \"\u002Fguides\u002Fnew-guide\u002F\"\n",[95,121,123],{"class":97,"line":122},5,[95,124,125],{},"  status = 301\n",[95,127,129],{"class":97,"line":128},6,[95,130,132],{"emptyLinePlaceholder":131},true,"\n",[95,134,136],{"class":97,"line":135},7,[95,137,107],{},[95,139,141],{"class":97,"line":140},8,[95,142,143],{},"  from = \"\u002Fapi\u002F*\"\n",[95,145,147],{"class":97,"line":146},9,[95,148,149],{},"  to = \"https:\u002F\u002Fapi.example.com\u002F:splat\"\n",[95,151,153],{"class":97,"line":152},10,[95,154,155],{},"  status = 200\n",[95,157,159],{"class":97,"line":158},11,[95,160,161],{},"  headers = { X-From = \"netlify\" }\n",[14,163,164,166,167,169],{},[18,165,61],{}," is compact for long lists generated by a script. ",[18,168,69],{}," is clearer for a handful of complex rules with conditions or headers. Using both is supported, but pick one as the primary source so people know where to look.",[171,172,173,335],"figure",{},[174,175,182,183,182,187,182,191,182,198,182,216],"svg",{"viewBox":176,"role":177,"ariaLabelledBy":178,"xmlns":181},"0 0 760 270","img",[179,180],"nrr-order-title","nrr-order-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[184,185,186],"title",{"id":179},"How Netlify evaluates a request against redirect rules",[188,189,190],"desc",{"id":180},"A request is matched against _redirects rules first, then netlify.toml rules, top to bottom. For each matching rule, Netlify checks whether a file exists at the path. If it does and the rule is not forced, the file is served. Otherwise the rule applies: a 301 or 302 redirects the browser, a 200 serves another path or proxies an external URL, and a 404 serves custom content.",[192,193],"rect",{"x":194,"y":194,"width":195,"height":196,"fill":197},"0","760","270","#ffffff",[199,200,201,202,182],"defs",{},"\n    ",[203,204,211],"marker",{"id":205,"viewBox":206,"refX":207,"refY":208,"markerWidth":209,"markerHeight":209,"orient":210},"nrr-order-arrow","0 0 10 10","9","5","7","auto-start-reverse",[212,213],"path",{"d":214,"fill":215},"M0,0 L10,5 L0,10 z","#556071",[217,218,201,220,201,227,201,235,201,241,201,247,201,252,201,255,201,260,201,265,201,269,201,273,201,277,201,283,201,289,201,293,201,298,201,301,201,305,201,309,201,313,201,319,201,323,201,328,201,331,182],"g",{"style":219},"font-family:system-ui, sans-serif;font-size:12px",[83,221,226],{"x":222,"y":223,"fill":224,"style":225},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","First matching rule, then the shadowing check",[192,228],{"x":229,"y":230,"width":231,"height":232,"rx":233,"fill":215,"style":234,"stroke":215},"20","96","120","50","8","fill-opacity:0.1",[83,236,240],{"x":237,"y":238,"fill":224,"style":239},"80","126","text-anchor:middle","request",[192,242],{"x":243,"y":237,"width":244,"height":245,"rx":233,"fill":246,"style":234,"stroke":246},"170","160","82","#166a9e",[83,248,251],{"x":249,"y":250,"fill":224,"style":239},"250","106","_redirects rules",[83,253,254],{"x":249,"y":238,"fill":224,"style":239},"then netlify.toml",[83,256,259],{"x":249,"y":257,"fill":215,"style":258},"146","font-size:11px;text-anchor:middle","top to bottom",[192,261],{"x":262,"y":237,"width":263,"height":245,"rx":233,"fill":264,"style":234,"stroke":264},"360","150","#8a6d0f",[83,266,268],{"x":267,"y":250,"fill":224,"style":239},"435","file exists at",[83,270,272],{"x":267,"y":271,"fill":224,"style":239},"124","source path and",[83,274,276],{"x":267,"y":275,"fill":224,"style":239},"142","rule not forced?",[192,278],{"x":279,"y":280,"width":281,"height":282,"rx":233,"fill":215,"style":234,"stroke":215},"550","46","190","60",[83,284,288],{"x":285,"y":286,"fill":224,"style":287},"645","72","font-weight:700;text-anchor:middle","yes: serve the file",[83,290,292],{"x":285,"y":291,"fill":215,"style":258},"92","rule is shadowed",[192,294],{"x":279,"y":295,"width":281,"height":296,"rx":233,"fill":297,"style":234,"stroke":297},"136","100","#3f6410",[83,299,300],{"x":285,"y":244,"fill":297,"style":287},"no: apply the rule",[83,302,304],{"x":285,"y":303,"fill":224,"style":239},"182","301\u002F302 → redirect",[83,306,308],{"x":285,"y":307,"fill":224,"style":239},"202","200 → rewrite or proxy",[83,310,312],{"x":285,"y":311,"fill":224,"style":239},"222","404 → custom content",[97,314],{"x1":315,"y1":316,"x2":317,"y2":316,"stroke":215,"style":318},"140","121","166","stroke-width:1.5px;marker-end:url(#nrr-order-arrow)",[97,320],{"x1":321,"y1":316,"x2":322,"y2":316,"stroke":215,"style":318},"330","356",[97,324],{"x1":325,"y1":326,"x2":327,"y2":237,"stroke":215,"style":318},"510","110","546",[97,329],{"x1":325,"y1":295,"x2":327,"y2":330,"stroke":215,"style":318},"176",[83,332,334],{"x":222,"y":333,"fill":215,"style":258},"258","add ! to the status (301!) to force a rule even when a file exists",[336,337,338],"figcaption",{},"Shadowing is why a redirect from a page that still exists appears to do nothing.",[32,340,342],{"id":341},"status-codes","Status Codes",[37,344,345,352,358,364],{},[40,346,347,351],{},[348,349,350],"strong",{},"301"," — permanent redirect. Browsers cache it; search engines move ranking signals to the new URL. Use for completed moves.",[40,353,354,357],{},[348,355,356],{},"302"," — temporary redirect. Not cached long-term. Use while testing, and for redirects that may change, such as \"latest version\" links.",[40,359,360,363],{},[348,361,362],{},"200"," — rewrite. The browser keeps the original URL and receives content from the target. Used for single-page app fallbacks, serving one folder under another path, and proxying.",[40,365,366,369,370,30],{},[348,367,368],{},"404"," — serve custom content with a 404 status, for example a section-specific not-found page: ",[18,371,372],{},"\u002Fdocs\u002F* \u002Fdocs\u002F404.html 404",[14,374,375],{},"Netlify also accepts 307 and 308, which behave like 302 and 301 but preserve the request method, relevant only when a form posts to a moved URL.",[32,377,379],{"id":378},"splats-and-placeholders","Splats and Placeholders",[14,381,382,383,386,387,390,391,394],{},"A splat (",[18,384,385],{},"*",") at the end of the source matches the rest of the path, available as ",[18,388,389],{},":splat"," in the target. Placeholders (",[18,392,393],{},":name",") match one path segment each:",[78,396,399],{"className":397,"code":398,"language":83,"meta":84},[81],"\u002Fblog\u002F:year\u002F:month\u002F:slug\u002F   \u002Farticles\u002F:slug\u002F   301\n\u002Fdocs\u002Fv1\u002F*                  \u002Fdocs\u002F:splat       301\n",[18,400,398],{"__ignoreMap":84},[14,402,403,404,407,408,411,412,30],{},"The first collapses thousands of date-based URLs from an old blog into one rule. The second retires a versioned docs path. Pattern rules are easier to review than long exact lists and cheaper to maintain, so look for patterns in a migration mapping before generating one line per URL. Query parameters can also be matched: ",[18,405,406],{},"\u002Fsearch q=:term \u002Ffind\u002F:term 301"," redirects ",[18,409,410],{},"\u002Fsearch?q=astro"," to ",[18,413,414],{},"\u002Ffind\u002Fastro",[32,416,418],{"id":417},"shadowing-and-forcing","Shadowing and Forcing",[14,420,421,422,425],{},"By default, Netlify serves a file if one exists at the requested path, even when a rule matches. This \"shadowing\" is intended: it lets a catch-all rewrite like ",[18,423,424],{},"\u002F* \u002Findex.html 200"," sit at the end of the file without hijacking real pages and assets.",[14,427,428,429,432],{},"It surprises people during migrations. If the old page still exists in the build output — because the generator still produces it, or a stale file remains — the redirect silently does nothing. Either remove the old file or force the rule with ",[18,430,431],{},"!",":",[78,434,437],{"className":435,"code":436,"language":83,"meta":84},[81],"\u002Fpricing-old\u002F   \u002Fpricing\u002F   301!\n",[18,438,436],{"__ignoreMap":84},[14,440,441,442,30],{},"Force only rules that need it. Forcing a catch-all rewrite would send every asset request to ",[18,443,444],{},"index.html",[14,446,447,448,451,452,455,456,459],{},"Shadowing also explains trailing-slash surprises. A rule from ",[18,449,450],{},"\u002Fpricing"," does not fire for a request to ",[18,453,454],{},"\u002Fpricing\u002F",", and Netlify's pretty URL handling may already serve ",[18,457,458],{},"\u002Fpricing\u002Findex.html"," for both. Write sources in the form your old site actually used, check the analytics or server logs from the old host for the exact variants readers requested, and add both forms where old links were inconsistent. A quick way to find shadowed rules after a deploy is to request every source path in the list and flag any that return 200 instead of the expected redirect status.",[32,461,463],{"id":462},"proxying-with-rewrites","Proxying With Rewrites",[14,465,466],{},"A 200 rule to an absolute URL makes Netlify fetch the target and return it under your domain. Common uses on static sites:",[37,468,469,478,488],{},[40,470,471,474,475,30],{},[348,472,473],{},"Avoiding CORS"," for a third-party API called from the browser: ",[18,476,477],{},"\u002Fapi\u002F* https:\u002F\u002Fapi.example.com\u002Fv2\u002F:splat 200",[40,479,480,483,484,487],{},[348,481,482],{},"Serving another deployment"," under a path: ",[18,485,486],{},"\u002Fblog\u002F* https:\u002F\u002Fblog-site.netlify.app\u002F:splat 200"," merges two sites under one domain.",[40,489,490,493],{},[348,491,492],{},"Analytics proxies"," so first-party requests reach an analytics endpoint.",[171,495,496,597],{},[174,497,182,502,182,505,182,508,182,511,182,518],{"viewBox":498,"role":177,"ariaLabelledBy":499,"xmlns":181},"0 0 760 220",[500,501],"nrr-proxy-title","nrr-proxy-desc",[184,503,504],{"id":500},"Redirect compared with a proxy rewrite",[188,506,507],{"id":501},"With a 301 redirect, the browser receives a Location header and makes a second request to the new host, whose URL appears in the address bar. With a 200 proxy rewrite, Netlify fetches the target itself and returns the response under the original URL, so the browser makes one same-origin request and no CORS check is needed.",[192,509],{"x":194,"y":194,"width":195,"height":510,"fill":197},"220",[199,512,201,513,182],{},[203,514,516],{"id":515,"viewBox":206,"refX":207,"refY":208,"markerWidth":209,"markerHeight":209,"orient":210},"nrr-proxy-arrow",[212,517],{"d":214,"fill":215},[217,519,201,520,201,523,201,529,201,533,201,538,201,541,201,545,201,548,201,552,201,556,201,560,201,565,201,569,201,572,201,574,201,577,201,579,201,581,201,583,201,585,201,588,201,592,182],{"style":219},[83,521,522],{"x":222,"y":223,"fill":224,"style":225},"Who makes the second request",[83,524,528],{"x":525,"y":526,"fill":224,"style":527},"30","62","font-weight:700","301 redirect",[192,530],{"x":525,"y":286,"width":231,"height":531,"rx":532,"fill":215,"style":234,"stroke":215},"34","6",[83,534,537],{"x":535,"y":536,"fill":224,"style":239},"90","94","browser",[192,539],{"x":540,"y":286,"width":315,"height":531,"rx":532,"fill":246,"style":234,"stroke":246},"300",[83,542,544],{"x":543,"y":536,"fill":224,"style":239},"370","Netlify",[192,546],{"x":547,"y":286,"width":315,"height":531,"rx":532,"fill":264,"style":234,"stroke":264},"590",[83,549,551],{"x":550,"y":536,"fill":224,"style":239},"660","api.example.com",[97,553],{"x1":263,"y1":245,"x2":554,"y2":245,"stroke":215,"style":555},"296","stroke-width:1.5px;marker-end:url(#nrr-proxy-arrow)",[83,557,559],{"x":558,"y":231,"fill":215,"style":258},"225","Location header back",[212,561],{"d":562,"fill":563,"stroke":564,"style":555},"M90,106 L90,126 L660,126 L660,110","none","#b32b30",[83,566,568],{"x":567,"y":231,"fill":564,"style":258},"500","browser calls the API (CORS applies)",[83,570,571],{"x":525,"y":244,"fill":224,"style":527},"200 proxy rewrite",[192,573],{"x":525,"y":243,"width":231,"height":531,"rx":532,"fill":215,"style":234,"stroke":215},[83,575,537],{"x":535,"y":576,"fill":224,"style":239},"192",[192,578],{"x":540,"y":243,"width":315,"height":531,"rx":532,"fill":246,"style":234,"stroke":246},[83,580,544],{"x":543,"y":576,"fill":224,"style":239},[192,582],{"x":547,"y":243,"width":315,"height":531,"rx":532,"fill":264,"style":234,"stroke":264},[83,584,551],{"x":550,"y":576,"fill":224,"style":239},[97,586],{"x1":263,"y1":587,"x2":554,"y2":587,"stroke":215,"style":555},"187",[97,589],{"x1":590,"y1":587,"x2":591,"y2":587,"stroke":297,"style":555},"440","586",[83,593,596],{"x":594,"y":595,"fill":297,"style":258},"513","180","Netlify fetches",[336,598,599],{},"A proxy keeps the request same-origin, which is why it removes CORS problems.",[14,601,602,603,606,607,610,611,613,614,616],{},"Proxied responses are cached by Netlify's CDN according to the target's ",[18,604,605],{},"Cache-Control"," headers. Add ",[18,608,609],{},"headers = { Authorization = \"...\" }"," in ",[18,612,69],{}," to send a header to the target, but never put secrets in ",[18,615,61],{},", which is published with the site.",[32,618,620],{"id":619},"country-and-language-rules","Country and Language Rules",[14,622,623],{},"Rules can match visitor country and browser language, which is useful for localised static sites:",[78,625,628],{"className":626,"code":627,"language":83,"meta":84},[81],"\u002F   \u002Fde\u002F   302   Language=de\n\u002F   \u002Ffr\u002F   302   Country=fr,be,ch  Language=fr\n\u002F   \u002Fen\u002F   302\n",[18,629,627],{"__ignoreMap":84},[14,631,632],{},"Order matters: specific rules first, then the fallback. Use 302, not 301, because the right destination depends on the visitor and should not be cached as permanent. Always provide a visible language switcher as well; geolocation and headers are hints, not the reader's choice.",[171,634,635,720],{},[174,636,182,641,182,644,182,647,182,650,182,657],{"viewBox":637,"role":177,"ariaLabelledBy":638,"xmlns":181},"0 0 760 240",[639,640],"nrr-geo-title","nrr-geo-desc",[184,642,643],{"id":639},"Language and country rules for the site root",[188,645,646],{"id":640},"A request for the root is checked against three rules in order. A browser preferring German goes to \u002Fde\u002F. A visitor from France, Belgium or Switzerland with French preferred goes to \u002Ffr\u002F. Everyone else goes to \u002Fen\u002F. All three use 302 redirects.",[192,648],{"x":194,"y":194,"width":195,"height":649,"fill":197},"240",[199,651,201,652,182],{},[203,653,655],{"id":654,"viewBox":206,"refX":207,"refY":208,"markerWidth":209,"markerHeight":209,"orient":210},"nrr-geo-arrow",[212,656],{"d":214,"fill":215},[217,658,201,659,201,662,201,664,201,667,201,670,201,674,201,677,201,680,201,683,201,687,201,691,201,694,201,697,201,703,201,705,201,708,201,712,201,714,201,716,182],{"style":219},[83,660,661],{"x":222,"y":223,"fill":224,"style":225},"Routing \"\u002F\" by language and country",[192,663],{"x":525,"y":230,"width":231,"height":232,"rx":233,"fill":215,"style":234,"stroke":215},[83,665,666],{"x":535,"y":238,"fill":224,"style":239},"GET \u002F",[192,668],{"x":510,"y":280,"width":540,"height":669,"rx":233,"fill":246,"style":234,"stroke":246},"40",[83,671,673],{"x":543,"y":672,"fill":224,"style":239},"71","Language=de",[192,675],{"x":510,"y":676,"width":540,"height":669,"rx":233,"fill":246,"style":234,"stroke":246},"101",[83,678,679],{"x":543,"y":238,"fill":224,"style":239},"Country=fr,be,ch and Language=fr",[192,681],{"x":510,"y":682,"width":540,"height":669,"rx":233,"fill":246,"style":234,"stroke":246},"156",[83,684,686],{"x":543,"y":685,"fill":224,"style":239},"181","no condition (fallback)",[83,688,690],{"x":689,"y":672,"fill":297,"style":527},"620","302 → \u002Fde\u002F",[83,692,693],{"x":689,"y":238,"fill":297,"style":527},"302 → \u002Ffr\u002F",[83,695,696],{"x":689,"y":685,"fill":297,"style":527},"302 → \u002Fen\u002F",[97,698],{"x1":263,"y1":699,"x2":700,"y2":701,"stroke":215,"style":702},"112","216","66","stroke-width:1.5px;marker-end:url(#nrr-geo-arrow)",[97,704],{"x1":263,"y1":316,"x2":700,"y2":316,"stroke":215,"style":702},[97,706],{"x1":263,"y1":707,"x2":700,"y2":330,"stroke":215,"style":702},"130",[97,709],{"x1":710,"y1":701,"x2":711,"y2":701,"stroke":215,"style":702},"520","612",[97,713],{"x1":710,"y1":316,"x2":711,"y2":316,"stroke":215,"style":702},[97,715],{"x1":710,"y1":330,"x2":711,"y2":330,"stroke":215,"style":702},[83,717,719],{"x":222,"y":718,"fill":215,"style":258},"226","only the root is routed; deep links keep the language the reader followed",[336,721,722],{},"Route only the entry point; never redirect a deep link to a different language.",[32,724,726],{"id":725},"testing-locally-and-in-previews","Testing Locally and in Previews",[14,728,729,732,733,736,737,741],{},[18,730,731],{},"netlify dev"," serves the site locally with the redirect engine applied, so rules can be checked with ",[18,734,735],{},"curl -I"," before pushing. Deploy previews run the same rules on real infrastructure; check the redirect list against the preview URL in CI, as described in ",[26,738,740],{"href":739},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fsetting-up-deploy-previews-on-netlify-for-every-pull-request\u002F","Netlify Deploy Previews for Every Pull Request",". Netlify's deploy summary also reports how many redirect rules were processed, which quickly reveals a file that was not copied into the publish directory.",[32,743,745],{"id":744},"measured-impact","Measured Impact",[14,747,748,749,751],{},"A content site moving from WordPress to Eleventy on Netlify needed 4,800 redirects. A generated ",[18,750,61],{}," file with three placeholder rules for date-based post URLs and 1,200 exact rules for pages covered them all. The first deploy showed 38 \"redirects\" that did nothing, all shadowed by old HTML files still produced by a legacy template; removing those files fixed them without forcing. Search Console reported the migration's crawl errors falling from 4,100 to 60 within three weeks.",[32,753,755],{"id":754},"pitfalls-rollback","Pitfalls & Rollback",[37,757,758,773,782,788,797],{},[40,759,760,765,766,769,770,30],{},[348,761,762,764],{},[18,763,61],{}," not in the publish directory."," It must be in the built output; many generators need it in ",[18,767,768],{},"public\u002F"," or ",[18,771,772],{},"static\u002F",[40,774,775,778,779,781],{},[348,776,777],{},"Catch-all before specific rules."," ",[18,780,424],{}," must be last.",[40,783,784,787],{},[348,785,786],{},"Chains."," Redirect old URLs straight to their final destination, not through intermediate moves, and re-check old rules whenever a page moves again.",[40,789,790,793,794,796],{},[348,791,792],{},"Secrets in proxy rules."," Put headers with credentials only in ",[18,795,69],{},", and prefer an edge function for anything sensitive.",[40,798,799,802],{},[348,800,801],{},"Rollback:"," Netlify deploys are atomic; publishing the previous deploy restores the previous rules.",[32,804,806],{"id":805},"conclusion","Conclusion",[14,808,809,810,812],{},"Netlify's redirect engine covers most routing needs of a static site without code: 301s for moves, 302s for temporary and conditional routing, 200 rewrites for fallbacks and proxies, and 404 rules for custom error pages. Keep rules in one primary file, order them from specific to general, remember that existing files shadow rules unless forced, test with ",[18,811,731],{}," and deploy previews, and generate long lists from a mapping rather than editing them by hand.",[32,814,816],{"id":815},"faq","FAQ",[818,819,821],"h3",{"id":820},"what-is-the-difference-between-a-redirect-and-a-rewrite-on-netlify","What is the difference between a redirect and a rewrite on Netlify?",[14,823,824],{},"A redirect (status 301 or 302) sends the browser to a new URL, which appears in the address bar. A rewrite (status 200) serves content from another path or URL while the browser keeps the original URL. Rewrites to external URLs act as a proxy.",[818,826,828],{"id":827},"why-is-my-netlify-redirect-being-ignored","Why is my Netlify redirect being ignored?",[14,830,831],{},"Most often because of shadowing. By default, a rule does not apply if a file exists at the source path. Add an exclamation mark after the status code, for example 301!, to force the rule even when a file exists.",[818,833,835],{"id":834},"should-i-use-_redirects-or-netlifytoml","Should I use _redirects or netlify.toml?",[14,837,838],{},"Either works and both can be used together; rules in _redirects are processed before those in netlify.toml. _redirects is compact for long lists, netlify.toml supports headers conditions and is easier to review for complex rules. Pick one as the main source to avoid confusion.",[818,840,842],{"id":841},"can-netlify-redirect-by-country-or-language","Can Netlify redirect by country or language?",[14,844,845],{},"Yes. Rules can include Country and Language conditions, matched against the visitor's geolocation and Accept-Language header, which is useful for sending visitors to a localised version of a static site.",[32,847,849],{"id":848},"related","Related",[37,851,852,860,867,874,881],{},[40,853,854,778,857,859],{},[348,855,856],{},"Parent:",[26,858,29],{"href":28}," — choosing and configuring a platform.",[40,861,862,866],{},[26,863,865],{"href":864},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy\u002F","Configuring Vercel for Hugo and Eleventy"," — redirects on Vercel.",[40,868,869,873],{},[26,870,872],{"href":871},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages\u002F","Configuring Redirects on Cloudflare Pages"," — the Cloudflare equivalent.",[40,875,876,880],{},[26,877,879],{"href":878},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-wordpress-to-a-static-site-generator\u002F","Migrating WordPress to a Static Site Generator"," — where redirect lists come from.",[40,882,883,887],{},[26,884,886],{"href":885},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function\u002F","Proxying Third-Party APIs from an Edge Function"," — when a proxy rule is not enough.",[889,890,891],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":84,"searchDepth":104,"depth":104,"links":893},[894,895,896,897,898,899,900,901,902,903,904,905,911],{"id":34,"depth":104,"text":35},{"id":54,"depth":104,"text":55},{"id":341,"depth":104,"text":342},{"id":378,"depth":104,"text":379},{"id":417,"depth":104,"text":418},{"id":462,"depth":104,"text":463},{"id":619,"depth":104,"text":620},{"id":725,"depth":104,"text":726},{"id":744,"depth":104,"text":745},{"id":754,"depth":104,"text":755},{"id":805,"depth":104,"text":806},{"id":815,"depth":104,"text":816,"children":906},[907,908,909,910],{"id":820,"depth":110,"text":821},{"id":827,"depth":110,"text":828},{"id":834,"depth":110,"text":835},{"id":841,"depth":110,"text":842},{"id":848,"depth":104,"text":849},[913,916,919,920],{"name":914,"item":915},"Home","\u002F",{"name":917,"item":918},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":29,"item":28},{"name":5,"item":921},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites\u002F","2026-09-18","Write Netlify redirects and rewrites in _redirects or netlify.toml: status codes, splats, placeholders, shadowing, proxying and country or language rules.","md",[926,927,928,929],{"q":821,"a":824},{"q":828,"a":831},{"q":835,"a":838},{"q":842,"a":845},{},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites",{"title":5,"description":923},"production-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites\u002Findex","article","7A2IoIBUKVRGqYRffs0I2ATlQAs08dGIGi2EkLeF5aw",[937,940,943,946,949,952,955,958,961,964,967,970,973,976,979,982,985,988,991,994,997,1000,1003,1006,1009,1012,1015,1018,1021,1024,1027,1030,1033,1035,1038,1041,1044,1047,1050,1053,1056,1059,1062,1065,1068,1071,1074,1077,1080,1083,1086,1089,1092,1095,1098,1101,1104,1107,1110,1113,1116,1119,1122,1125,1128,1131,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215,1218,1221,1224,1227,1230,1233,1236,1239,1242,1245,1248,1251,1254,1257,1260,1263,1266,1269,1272,1275,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1372,1374,1377,1378,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455,1458,1461,1464,1467,1470,1473,1476],{"path":938,"title":939},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages","Astro vs Eleventy Build Times at 10,000 Pages",{"path":941,"title":942},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fchoosing-between-astro-and-eleventy-for-large-docs","Astro vs Eleventy for Large Docs (1000+ Pages)",{"path":944,"title":945},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade","Content Collections vs the Eleventy Data Cascade",{"path":947,"title":948},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":950,"title":951},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors","Shortcodes vs Components for Docs Authors",{"path":953,"title":954},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsidebar-navigation-in-astro-and-eleventy","Sidebar Navigation in Astro and Eleventy",{"path":956,"title":957},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme","Customizing Starlight Without Forking the Theme",{"path":959,"title":960},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation","Docusaurus vs Starlight for Product Documentation",{"path":962,"title":963},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":965,"title":966},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content","MDX vs Markdoc for Docs Content",{"path":968,"title":969},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":971,"title":972},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":974,"title":975},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":977,"title":978},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhow-to-benchmark-hugo-vs-astro-build-speeds","How to Benchmark Hugo vs Astro Build Speeds",{"path":980,"title":981},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds","Hugo partialCached for Faster Builds",{"path":983,"title":984},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":986,"title":987},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fprofiling-hugo-templates-with-template-metrics","Profiling Hugo Templates With Template Metrics",{"path":989,"title":990},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners","Reducing Hugo Memory Usage on CI Runners",{"path":992,"title":993},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fspeeding-up-hugo-builds-with-render-hooks-and-caching","Speeding Up Hugo Builds with Render Hooks & Caching",{"path":995,"title":996},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":998,"title":999},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Feleventy-vs-jekyll-for-markdown-heavy-blogs","Eleventy vs Jekyll for Markdown-Heavy Blogs",{"path":1001,"title":1002},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1004,"title":1005},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Freplacing-jekyll-plugins-when-migrating-to-eleventy","Replacing Jekyll Plugins When Migrating to Eleventy",{"path":1007,"title":1008},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-on-github-pages-without-plugins","Running Jekyll on GitHub Pages Without Plugins",{"path":1010,"title":1011},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1013,"title":1014},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1016,"title":1017},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fconverting-front-matter-at-scale-during-migration","Converting Front Matter at Scale During Migration",{"path":1019,"title":1020},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1022,"title":1023},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration","Keeping Redirects Working After an SSG Migration",{"path":1025,"title":1026},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-docs-site-from-jekyll-to-hugo","Migrating a Docs Site From Jekyll to Hugo",{"path":1028,"title":1029},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1031,"title":1032},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-hugo-to-astro-without-breaking-urls","Migrating From Hugo to Astro Without Breaking URLs",{"path":1034,"title":879},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-wordpress-to-a-static-site-generator",{"path":1036,"title":1037},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fporting-shortcodes-and-includes-between-generators","Porting Shortcodes and Includes Between Generators",{"path":1039,"title":1040},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export","Handling Dynamic Routes in Next.js Static Export",{"path":1042,"title":1043},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1045,"title":1046},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fmigrating-from-gatsby-to-nextjs-static-export","Migrating from Gatsby to Next.js Static Export",{"path":1048,"title":1049},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-app-router-static-export-limitations","Next.js App Router Static Export Limitations",{"path":1051,"title":1052},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-astro-for-marketing-sites","Next.js Static Export vs Astro for Marketing",{"path":1054,"title":1055},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Foptimizing-images-in-nextjs-static-export","Optimizing Images in Next.js Static Export",{"path":1057,"title":1058},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fadding-pagefind-to-an-astro-site","Adding Pagefind to an Astro Site",{"path":1060,"title":1061},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fbuilding-a-lunr-index-at-build-time-in-eleventy","Building a Lunr Index at Build Time in Eleventy",{"path":1063,"title":1064},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1066,"title":1067},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1069,"title":1070},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1072,"title":1073},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1075,"title":1076},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs","Search Index Size Budgets for Large Docs",{"path":1078,"title":1079},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience","Best SSG for Non-Developer Technical Writers",{"path":1081,"title":1082},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-api-reference-documentation","Choosing an SSG for API Reference Documentation",{"path":1084,"title":1085},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1087,"title":1088},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1090,"title":1091},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fpicking-an-ssg-for-a-multi-language-documentation-site","Picking an SSG for a Multi-Language Docs Site",{"path":1093,"title":1094},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fssg-selection-checklist-for-engineering-teams","SSG Selection Checklist for Engineering Teams",{"path":1096,"title":1097},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Ftotal-cost-of-ownership-for-static-site-generators","Total Cost of Ownership for Static Site Generators",{"path":1099,"title":1100},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames","Cache Busting with Content-Hashed Filenames",{"path":1102,"title":1103},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1105,"title":1106},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fpurging-the-cdn-cache-after-a-static-deploy","Purging the CDN Cache After a Static Deploy",{"path":1108,"title":1109},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-cache-control-headers-on-cloudflare-pages","Cache-Control Headers on Cloudflare Pages",{"path":1111,"title":1112},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-up-proper-cache-headers-on-netlify","Proper Cache Headers on Netlify for SSGs",{"path":1114,"title":1115},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html","Stale-While-Revalidate for Static HTML",{"path":1117,"title":1118},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Feliminating-layout-shift-from-web-fonts","Eliminating Layout Shift From Web Fonts",{"path":1120,"title":1121},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-cookie-banners","Fixing CLS from Cookie Banners",{"path":1123,"title":1124},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-late-loading-embeds","Fixing CLS From Late-Loading Embeds",{"path":1126,"title":1127},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-sticky-headers-and-anchor-links","Fixing CLS from Sticky Headers and Anchor Links",{"path":1129,"title":1130},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1132,"title":1133},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fmeasuring-cls-in-the-field-with-web-vitals-js","Measuring CLS in the Field With web-vitals.js",{"path":1135,"title":1136},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-images-and-embeds-to-stop-layout-shift","Reserving Space for Images and Embeds",{"path":1138,"title":1139},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1141,"title":1142},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1144,"title":1145},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fmetric-matched-fallback-fonts-with-size-adjust","Metric-Matched Fallback Fonts with size-adjust",{"path":1147,"title":1148},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1150,"title":1151},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosting-google-fonts-to-eliminate-layout-shift","Self-Host Google Fonts to Eliminate Layout Shift",{"path":1153,"title":1154},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fsubsetting-variable-fonts-for-faster-first-render","Subsetting Variable Fonts for Faster First Render",{"path":1156,"title":1157},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fbuilding-an-image-cdn-pipeline-for-static-sites","Building an Image CDN Pipeline for Static Sites",{"path":1159,"title":1160},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fgenerating-open-graph-images-at-build-time","Generating Open Graph Images at Build Time",{"path":1162,"title":1163},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1165,"title":1166},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Flazy-loading-images-without-hurting-lcp","Lazy-Loading Images Without Hurting LCP",{"path":1168,"title":1169},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins","Optimizing WebP Images in Hugo Without Plugins",{"path":1171,"title":1172},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fresponsive-images-with-srcset-in-eleventy","Responsive Images with srcset in Eleventy",{"path":1174,"title":1175},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-avif-with-fallbacks-on-static-sites","Serving AVIF With Fallbacks on Static Sites",{"path":1177,"title":1178},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1180,"title":1181},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1183,"title":1184},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro","Deferring Hydration with client:visible in Astro",{"path":1186,"title":1187},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fhow-to-reduce-bundle-size-in-eleventy-builds","How to Reduce Bundle Size in Eleventy Builds",{"path":1189,"title":1190},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1192,"title":1193},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fmeasuring-inp-on-static-sites-with-real-user-monitoring","Measuring INP on Static Sites with RUM",{"path":1195,"title":1196},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1198,"title":1199},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Feliminating-render-blocking-css-on-static-sites","Eliminating Render-Blocking CSS on Static Sites",{"path":1201,"title":1202},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-on-text-heavy-documentation-pages","Fixing LCP on Text-Heavy Documentation Pages",{"path":1204,"title":1205},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1207,"title":1208},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools","Measuring LCP Subparts with DevTools",{"path":1210,"title":1211},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Foptimizing-lcp-on-astro-with-priority-hints","Optimizing LCP on Astro with Priority Hints",{"path":1213,"title":1214},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Freducing-lcp-from-hero-images-on-static-sites","Reducing LCP from Hero Images on Static Sites",{"path":1216,"title":1217},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux","Comparing Lab and Field Data with CrUX",{"path":1219,"title":1220},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1222,"title":1223},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci","Reducing Lighthouse Score Variance in CI",{"path":1225,"title":1226},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys","Running WebPageTest Scripts Against Preview Deploys",{"path":1228,"title":1229},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site","Setting Up Lighthouse CI for a Static Site",{"path":1231,"title":1232},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request","Tracking Bundle Size per Pull Request",{"path":1234,"title":1235},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds","Writing a Performance Budget That Fails Builds",{"path":1237,"title":1238},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1240,"title":1241},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1243,"title":1244},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1246,"title":1247},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fpreconnect-vs-dns-prefetch-on-static-sites","Preconnect vs DNS-Prefetch on Static Sites",{"path":1249,"title":1250},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1252,"title":1253},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-on-multi-page-static-sites","View Transitions on Multi-Page Static Sites",{"path":1255,"title":1256},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fauditing-third-party-scripts-with-lighthouse","Auditing Third-Party Scripts With Lighthouse",{"path":1258,"title":1259},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1261,"title":1262},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Flazy-loading-youtube-embeds-on-static-sites","Lazy-Loading YouTube Embeds on Static Sites",{"path":1264,"title":1265},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Floading-google-tag-manager-without-hurting-inp","Loading Google Tag Manager Without Hurting INP",{"path":1267,"title":1268},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Frunning-third-party-scripts-in-a-web-worker-with-partytown","Running Third-Party Scripts in a Web Worker with Partytown",{"path":1270,"title":1271},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fself-hosting-analytics-to-cut-third-party-requests","Self-Hosting Analytics to Cut Third-Party Requests",{"path":1273,"title":1274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1276,"title":872},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages",{"path":1278,"title":1279},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcustom-domains-and-tls-on-cloudflare-pages","Custom Domains and TLS on Cloudflare Pages",{"path":1281,"title":1282},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-hugo-to-cloudflare-pages-and-workers","Deploying Hugo to Cloudflare Pages and Workers",{"path":1284,"title":1285},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1287,"title":1288},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets","Migrating from Cloudflare Pages to Workers Static Assets",{"path":1290,"title":1291},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1293,"title":1294},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fdocs-as-code-review-workflow-for-writers","Docs-as-Code Review Workflow for Writers",{"path":1296,"title":1297},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1299,"title":1300},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1302,"title":1303},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduling-content-publication-with-cron-triggered-builds","Scheduling Content Publication With Cron-Triggered Builds",{"path":1305,"title":1306},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fwiring-a-headless-cms-to-a-static-build","Wiring a Headless CMS to a Static Build",{"path":1308,"title":1309},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1311,"title":1312},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fcaching-node-modules-in-github-actions-for-faster-ssg-builds","Caching node_modules in GitHub Actions",{"path":1314,"title":1315},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1317,"title":1318},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow","Deploying to Multiple Environments From One Workflow",{"path":1320,"title":1321},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fhow-to-set-up-github-actions-for-hugo-deployments","GitHub Actions for Hugo Deployments",{"path":1323,"title":1324},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1326,"title":1327},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1329,"title":1330},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions","Caching Hugo Builds in GitHub Actions",{"path":1332,"title":1333},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1335,"title":1336},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-builds-in-astro-with-the-content-layer","Incremental Builds in Astro with the Content Layer",{"path":1338,"title":1339},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1341,"title":1342},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci","Measuring Build-Time Regressions in CI",{"path":1344,"title":1345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos","Remote Caching with Turborepo for SSG Monorepos",{"path":1347,"title":1348},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners","Sharing Build Cache Across CI Runners",{"path":1350,"title":1351},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1353,"title":1354},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1356,"title":1357},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data","Building a Core Web Vitals Dashboard from RUM Data",{"path":1359,"title":1360},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fcrawling-for-broken-links-on-a-schedule","Crawling for Broken Links on a Schedule",{"path":1362,"title":1363},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1365,"title":1366},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1368,"title":1369},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fuptime-and-synthetic-checks-for-static-sites","Uptime and Synthetic Checks for Static Sites",{"path":1371,"title":865},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy",{"path":1373,"title":29},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies",{"path":1375,"title":1376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":931,"title":5},{"path":1379,"title":740},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fsetting-up-deploy-previews-on-netlify-for-every-pull-request",{"path":1381,"title":1382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs","Vercel ISR vs Static Generation for SSGs",{"path":1384,"title":1385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fautomating-preview-deploy-pipelines-with-github-actions","Automating Preview Deploy Pipelines with GitHub Actions",{"path":1387,"title":1388},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1390,"title":1391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1393,"title":1394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1396,"title":1397},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1399,"title":1400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1402,"title":1403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1405,"title":1406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1408,"title":1409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1411,"title":1412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1414,"title":1415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute","Rolling Back a Bad Static Deploy in Under a Minute",{"path":1417,"title":1418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url","Running Smoke Tests Against a Preview URL",{"path":1420,"title":1421},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1423,"title":1424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1426,"title":1427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fhash-based-csp-for-inline-scripts-in-astro","Hash-Based CSP for Inline Scripts in Astro",{"path":1429,"title":1430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1432,"title":1433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1435,"title":1436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1438,"title":1439},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site","Writing a Content Security Policy for a Static Site",{"path":1441,"title":1442},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1444,"title":1445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1447,"title":1448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fdeploying-a-static-site-to-s3-and-cloudfront","Deploying a Static Site to S3 and CloudFront",{"path":1450,"title":1451},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1453,"title":1454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1456,"title":1457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1459,"title":1460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1462,"title":1463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fadding-a-contact-form-with-cloudflare-workers","Adding a Contact Form with Cloudflare Workers",{"path":1465,"title":1466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fhandling-form-submissions-on-a-static-site","Handling Form Submissions on a Static Site",{"path":1468,"title":1469},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1471,"title":1472},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1474,"title":1475},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1477,"title":886},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function",1789722848245]