1
00:00:00,080 --> 00:00:04,282
When one website loops at sign-in or remembers an unwanted state,

2
00:00:04,282 --> 00:00:07,433
clearing all Chrome cookies is a broad first move.

3
00:00:07,433 --> 00:00:10,935
This tutorial follows Google's current one-site path instead.

4
00:00:10,935 --> 00:00:14,786
The goal is to remove the stored data for the exact

5
00:00:14,786 --> 00:00:17,238
website you choose, then retry that site.

6
00:00:17,238 --> 00:00:21,089
Save any unfinished form or shopping cart first, because the selected

7
00:00:21,089 --> 00:00:22,840
site may sign you out.

8
00:00:23,440 --> 00:00:27,191
Before opening settings, write down the site name from the address

9
00:00:27,191 --> 00:00:30,260
bar and note whether you are signed in there.

10
00:00:30,260 --> 00:00:33,671
Our worksheet uses a fictional support portal as the example.

11
00:00:33,671 --> 00:00:38,104
Do not use your Google account or a banking site for casual practice.

12
00:00:38,104 --> 00:00:41,855
The search result can show several related entries, so the domain

13
00:00:41,855 --> 00:00:45,607
and its subdomains deserve a careful second look before deleting anything.

14
00:00:46,207 --> 00:00:50,078
In desktop Chrome, open Settings, choose Privacy and security, then

15
00:00:50,078 --> 00:00:54,337
Third-party cookies, and open See all site data and permissions.

16
00:00:54,337 --> 00:00:57,434
Google documents that path for deleting specific cookies.

17
00:00:57,434 --> 00:01:02,080
The label may move as Chrome changes, so use the page's

18
00:01:02,080 --> 00:01:04,790
current wording rather than a remembered screenshot.

19
00:01:04,790 --> 00:01:09,823
Do not choose the broader Delete browsing data command for this targeted exercise.

20
00:01:10,423 --> 00:01:15,808
Use the search field in the site-data list and enter the target site's name.

21
00:01:15,808 --> 00:01:18,164
Read each matching hostname before touching Remove.

22
00:01:18,164 --> 00:01:22,875
A parent domain and a subdomain may not be the same stored-data entry.

23
00:01:22,875 --> 00:01:27,587
If the results include an unrelated website with a similar name, leave it alone.

24
00:01:27,587 --> 00:01:32,299
The purpose of this pause is to make the removal scope visible and deliberate.

25
00:01:32,899 --> 00:01:37,932
For the intended entry, choose its Remove control and confirm Delete when Chrome asks.

26
00:01:37,932 --> 00:01:41,887
Google says deleting cookies can sign you out of sites that

27
00:01:41,887 --> 00:01:44,762
remember you and can erase saved site preferences.

28
00:01:44,762 --> 00:01:47,279
That is expected for the selected website.

29
00:01:47,279 --> 00:01:51,952
This does not clear every website's cookies, but shared sign-in systems

30
00:01:51,952 --> 00:01:55,907
can still cause related services to ask you to authenticate again.

31
00:01:56,507 --> 00:01:58,466
Reload only the website you targeted.

32
00:01:58,466 --> 00:02:02,057
The stale state may be gone, or the site may ask

33
00:02:02,057 --> 00:02:03,690
you to sign in again.

34
00:02:03,690 --> 00:02:07,281
If the original problem persists, cookies were not the whole cause;

35
00:02:07,281 --> 00:02:09,241
do not repeatedly clear unrelated data.

36
00:02:09,241 --> 00:02:12,832
The worksheet asks you to confirm that the target entry disappeared

37
00:02:12,832 --> 00:02:17,403
from Chrome's list and that you did not run a browser-wide clear.

38
00:02:18,003 --> 00:02:21,704
If a single site misbehaves again, start by checking its URL,

39
00:02:21,704 --> 00:02:24,059
saved work, and current site-data entry.

40
00:02:24,059 --> 00:02:28,096
Keep the one-site path in your notes; it is easier to

41
00:02:28,096 --> 00:02:32,132
reverse a sign-in disruption on one site than on every site.

42
00:02:32,132 --> 00:02:36,169
If the site is still broken after a fresh sign-in, consult

43
00:02:36,169 --> 00:02:39,870
that site's status or support before making broader browser changes.