Keyword Prominence Checker
Check where a keyword appears on a page, not just how often.
Build caching headers without guessing what the directives do.
Directives
Your generated code appears here.
The Cache-Control Header Generator builds caching headers from presets for the common cases, explaining each directive as you pick it — including the ones that do the opposite of what they sound like. no-cache does not mean do not cache; that is no-store. The Apache and nginx configuration to set the header is written alongside it.
Pick what you are serving and the generator writes the Cache-Control header for it, with every directive explained in the panel beside it and the matching Apache and nginx configuration produced underneath.
Caching is one of the few things that is both high-impact and almost free, and it is consistently done badly because the directives are unintuitive. no-cache does not mean do not cache — it means cache this but revalidate before using it; the directive for do not cache is no-store. public and private describe whether shared caches may hold a copy, not whether the content is secret. And immutable, the one that actually matters for fingerprinted assets, stops a browser revalidating on refresh, which is where a surprising amount of latency hides. Presets for the common cases are here so you can start from something correct.
Fingerprinted assets, HTML pages, images, API responses and private content each start from the right place.
no-cache versus no-store, public versus private — the two pairs people reliably get backwards.
The directive that removes a revalidation round trip on every refresh, which most sites still pay.
A sentence saying what browsers and CDNs will actually do, so a wrong tick is obvious.
The Apache and nginx directives, not just the header value.
An HTML page, a fingerprinted asset, an image, an API response or something private.
Each one is explained as you tick it, including the ones that do the opposite of what they sound like.
A sentence describing what browsers and CDNs will actually do with it.
The raw header, plus the Apache and nginx directives that set it.
no-cache allows caching but requires revalidation before the copy is used. no-store forbids storing the response at all. They sound like synonyms and they are opposites in effect — no-store is the one for anything genuinely sensitive.
For a fingerprinted asset whose filename changes when its content does, one year with immutable. For an HTML page, minutes or no-cache, since you want changes to appear. For an image that could be replaced under the same name, hours to days.
It tells the browser the file will never change at that URL, so it need not revalidate even when the user hits refresh. For fingerprinted build output that is exactly true, and it removes a round trip that most sites still pay on every reload.
No. Cache-Control supersedes it and takes precedence wherever both are present. Sending both is harmless and mostly a habit from supporting browsers that have not existed for a long time.
What people who use the Cache-Control Header Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Cache-Control Header Generator. It takes half a minute and no account.
Write the first reviewCheck where a keyword appears on a page, not just how often.
Find the words and phrases your copy actually leans on.
Write the canonical link tag, and check it points somewhere sensible.
Pull the domains out of a list of URLs and count them.
Cross three lists of words into every combination.
Turn a list of old and new URLs into Apache redirect rules.
Check a sitemap for the errors that make Google reject it.
Address, hours, phone and geo as LocalBusiness JSON-LD.