Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo set up a Cloudflare Page Rule, open your domain’s Rules > Page Rules page, create a rule with a URL pattern, choose its settings, set its priority, and deploy it. The matching hostname must be proxied through Cloudflare, and only the highest-priority matching Page Rule applies to a request.
Before you create a Page Rule
- Check DNS proxying. The hostname in the pattern must have a DNS record proxied through Cloudflare. A hostname missing from DNS or not routed through Cloudflare will not match in practice. If a hostname has no origin, Cloudflare says a proxied placeholder record may still be needed; use a reserved IP address or domain, not infrastructure you do not control. See Cloudflare’s Page Rules overview and Page Rules management guide.
- Know the limit. Cloudflare’s Page Rules overview, last updated August 14, 2026, lists default zone quotas of 3 for Free, 20 for Pro, 50 for Business, and 125 for Enterprise. Disabled rules count toward the allowance.
- Plan the order. Only the highest-priority matching Page Rule takes effect. Put narrow patterns above broad ones; for example, put
example.com/images/special/*aboveexample.com/images/*.
Create and deploy a Page Rule
- In the Cloudflare dashboard, select the domain.
- Open Rules > Page Rules, then choose Create Page Rule.
- Enter a URL pattern and choose the setting or settings the rule should apply.
- Choose the rule’s order. Place specific patterns before any broader pattern that could also match.
- Choose Save and Deploy Page Rule to activate it, or Save as Draft if it is not ready to go live.
Cloudflare’s pattern format is generally <SCHEME>://<HOSTNAME>:<PORT>/<PATH>?<QUERY_STRING>. Scheme and port are optional; if omitted, the pattern can match both HTTP and HTTPS and all ports. A Page Rule can apply multiple settings, but the API documentation says a redirect action cannot be combined with setting overrides in the same action set. See Cloudflare’s pattern-matching reference and Page Rules API documentation.
Useful Page Rule examples
These examples are based on Cloudflare’s documented configurations. Replace example domains and paths with your own, and check that the pattern matches only the intended requests.
Redirect www to the root domain
To send visitors from www.example.com to example.com, Cloudflare documents a 301 permanent redirect using the pattern *www.example.com/* and target https://example.com/$2. Use a 301 only when the move is intended to be permanent. Before deploying, validate how the wildcard captures are substituted for your actual URL patterns. See Cloudflare’s Page Rules examples.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteMake a temporary short link
A short path such as /fb* can redirect to a longer destination with a 302 temporary status. Choose 302 when the source URL may return or the destination may change; use a permanent status only for a lasting move. Cloudflare’s example is in its Page Rules examples.
Bypass cache on a user or admin path
Cloudflare shows the pattern example.com/user* with Cache Level: Bypass. This can be appropriate for user-specific or frequently changing content that should be fetched from the origin. Adapt the pattern to your application’s private and dynamic routes rather than assuming one path covers them all. See Cloudflare’s examples and Page Rules settings reference.
Rank #2
Set longer cache times for stable assets
For a directory that contains cache-safe image and multimedia assets, Cloudflare’s example combines Browser Cache TTL: one day, Cache Level: Cache Everything, and Edge Cache TTL: seven days. These are example values, not universal defaults. Confirm that the path does not include dynamic or private content and that the application and origin are compatible.
Cloudflare defines Cache Everything as treating all content types as cacheable, beyond its default static-file behavior. Its settings documentation warns that combining Cache Everything with an Edge Cache TTL greater than zero removes cookies from the origin response. Review your cache headers and the full behavior before using it on dynamic pages. Details are in the settings reference and Cloudflare’s examples.
Free tools Windows power users keep installed
One-click scans. No signup required.
When to use a newer Cloudflare Rules product
Page Rules can trigger actions from URL patterns, but Cloudflare advises considering newer products when they offer a better fit. Its current documentation describes these options:
| Need | Cloudflare product | Documented fit |
|---|---|---|
| Zone-level redirects | Single Redirects | Static or dynamic redirects |
| Many redirects | Bulk Redirects | Larger account-level sets of mostly static redirects |
| More flexible JavaScript-based behavior | Snippets | Custom behavior beyond a straightforward redirect |
| Cache customization | Cache Rules | Rules for customizing caching behavior |
Cloudflare says these newer products are available on all plans, though quotas and features depend on the plan. See its Rules documentation, URL forwarding documentation, and Cache Rules guide. Existing Page Rules do not all have to be migrated; check whether each one still does the job before adding or replacing rules.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
