When one website keeps showing a broken page or a sign-in loop in desktop Chrome, deleting every cookie can disrupt unrelated accounts. A more focused test is to remove the affected site’s stored data, after saving work and confirming you can sign in again.
This guide explains that specific cleanup step. If you have not narrowed the problem to one site, start with our Chrome loading-error guide.
1. Decide whether a targeted cleanup makes sense
Write down the exact address and symptom. Compare a familiar unrelated website. If many sites fail, deleting one site’s data is unlikely to address the wider problem.
If the affected service also fails on another device, check its official support or status page first. A widespread service fault does not become a local cookie problem just because Chrome displays it.
A page working in a fresh session is a clue, not proof: the account, extensions and stored data can differ. Choose one change at a time so you can tell which result followed it.
2. Protect work and account access first
Save or copy unfinished text and finish uploads before removing data. Do not assume a draft exists on the server simply because it remains visible in a tab. If an order or payment was submitted, check its confirmation before retrying.
Google warns that deleting cookies can sign you out and remove saved preferences. Make sure you have your usual sign-in method and access to any required verification device. Do not publish passwords or recovery codes when asking for help.
Site data can also include local browser storage, as explained in Google’s browsing-data documentation. Treat unsynced or offline work cautiously. For a work or school service, ask IT if you are unsure what is stored locally.
3. Find the site in Chrome’s settings
- Open Chrome’s three-dot menu and select Settings.
- Select Privacy and security → Third-party cookies.
- Open See all site data and permissions.
- Search for the website’s name and inspect the matching domain.
- Use the delete control next to the intended site, then confirm Delete only after checking the target.
This is the route in Google’s current desktop cookie instructions. Labels can change between versions. If your settings differ, consult the linked instructions rather than selecting a similarly named broad deletion command.
Search matches can include multiple addresses. For example, an account page and a service page may use different subdomains. Do not remove every vaguely related result. Identify the site involved; stop and ask support if the grouping or confirmation is unclear.
4. Reopen and test the same task
Return to the site through a known address, reload it and sign in if prompted. Test the original problem once: does the page finish loading, and does the normal sign-in remain usable?
- It works: record that the targeted cleanup helped. This does not identify the exact faulty cookie or guarantee the problem cannot return.
- It still fails: preserve the error and comparison results. Move to the broader Chrome checks rather than repeatedly removing more domains.
- You cannot sign in: use the service’s official recovery process. Clearing data does not repair an account lockout.
5. Keep privacy and security checks separate
Removing site data is different from granting camera access, allowing third-party cookies globally or bypassing certificate warnings. Do not make those extra changes just to force a page to work. If the symptom concerns access to a camera or location, use our Chrome permissions guide.
If support is needed, provide the domain, exact error, Chrome version, whether other sites work and whether targeted cleanup changed anything. Redact private information from screenshots. This guide is based on official documentation, not hands-on testing of your account or browser.
Was this helpful?
Help us make our guides more useful.
No sign-in needed. This browser remembers your response for up to 180 days.