Idempotency key
Related service Websites, web apps & online shops
DEFINITION
An idempotency key is a client-generated unique identifier (usually a UUID) sent in a request header (Idempotency-Key) on every state-changing POST, PUT, or DELETE. Payment APIs (Stripe, Adyen, SimplePay, PayPal) use it to guarantee that if the same key arrives twice (because the network dropped, the client retried, the load balancer retried), the operation runs exactly once and the second response is the cached first response. Without it, a client retrying after a 30-second timeout charges the customer 100 thousand forints twice. Retry logic must not exist without an idempotency key on the payment, order placement, email send, and webhook delivery layers. Worth doing on your own API too: put a Postgres unique index on the key, and de-duplicate either at the call boundary or on the event queue.
- Answer Engine Optimization (AEO)→
We shape content so AI answer engines (ChatGPT, Perplexity, Google AI overviews) cite YOU: clear claims, structure, sources, schema. The successor discipline to classic SEO in 2026.
- Zero-Click Search→
Searches resolved right on the results page (AI overview, snippet) with no click to any site. Rising fast: you win by being the cited source, not just by ranking.
- Featured Snippet→
The boxed answer Google lifts to the top ("position zero"). Win it with a crisp, directly-phrased answer placed right under a question heading.
- People Also Ask→
Google's expanding box of related questions. Each one is a content opportunity: answer them explicitly to capture the box and the long-tail traffic.
- Crawl Budget→
How many pages a search engine will crawl on your site per visit. It matters for large sites: waste it on junk URLs and your important pages get crawled late.
- Canonical URL→
The <link rel="canonical"> that tells search engines which URL is the master when duplicates or params exist. Prevents ranking signals from being diluted across near-identical pages.