Scroll Top

HTTP 404 Bad Request: What the Error Means

Updated September 2026 · Written and maintained by the Progression Agency strategy team

An HTTP 404 bad request is not one error, it is two — and knowing which one you are actually looking at is most of the fix. A 404 means the server understood your request perfectly and has nothing at that address. A 400 Bad Request means the server could not understand the request at all. They have different causes, different fixes and different consequences, and browsers sometimes present them in ways that blur the two. This page separates them, then covers 404 bad gateway confusion, and finishes with what a site owner should actually do about broken URLs.

The short answerA 404 means the page does not exist at that address: check the URL for typos, load the domain on its own to confirm the site is up, and search the site in case the page moved. A 400 Bad Request means the request itself was malformed: open the site in a private window, and if that works, clear the cookies for that one site — an oversized cookie header is the most common browser-side cause. A 502 Bad Gateway is neither of those; it means a server upstream returned an invalid response and there is nothing you can do from your side. If you own the site, the fix for a 404 is a 301 redirect to the closest genuine equivalent, a 410 for pages retired deliberately, and repairing the internal link that pointed at the dead URL in the first place.

HTTP errors, distinguished
A 404 bad request is two different errors described as one. Separating them is the whole diagnostic step, because a 404 is about the address and a 400 is about the request.

What is a 404 error?

HTTP 404 Not Found means the server received and understood your request and there is no resource at that address. The request was valid; the address was not. That distinction is what separates it from every other error on this page.

A 404 does not mean the site is down. It means one specific address on it does not resolve. The fastest confirmation is to delete everything after the domain and load the homepage: if that works, the site is fine and the path is wrong.

Common causes of a 404

  • A typo or a truncated paste in the address.
  • A page that was renamed or moved without a redirect being put in place.
  • A page deliberately deleted by the site owner.
  • An internal link on the site still pointing at an old address.
  • An external site linking to a URL that changed years ago.
  • Case sensitivity: some servers treat /Page and /page as different addresses.
  • Trailing slash inconsistency between the link and the server’s expectation.

Is a 404 always a problem?

No. Returning 404 for something that genuinely does not exist is correct behavior, and a site with no 404s at all is usually one that redirects everything to its homepage, which is worse. A 404 becomes a problem when it replaces a page that had traffic or inbound links.

What is a 400 Bad Request?

HTTP 400 Bad Request means the server could not understand the request. Something in what your browser sent was malformed — the URL syntax, a header, or most often a cookie that has grown too large. Unlike a 404, this one is frequently caused on your side and frequently fixable in under a minute.

Whose problem is it? Reading the error correctly
Yes means you can usually fix it yourself from the browser side. No means the server or the site owner has to. Partial means it could be either, and the next step is to check whether it happens in a private window.

The scorecard above is a triage tool. Anything marked yes is usually resolvable from the browser; anything marked no requires the server operator. The partial rows are the ones worth testing in a private window first, because that single step tells you which side the problem sits on.

Causes of a 400 error you can fix yourself

  1. An oversized or corrupted cookie for that specific site. This is the most common cause.
  2. A malformed URL, often from a paste that included a stray character or a line break.
  3. Invalid characters in the address that were not encoded properly.
  4. A request header made too large by a browser extension.
  5. A stale cached redirect pointing at a malformed address.

How to fix a 400 error in three steps

  1. Open the same URL in a private or incognito window. If it loads, the problem is local state.
  2. If it loaded privately, clear the cookies and site data for that one site only.
  3. Reload the original window. If it still fails, retype the URL by hand rather than pasting.

Clearing cookies for one site is deliberate advice: clearing everything logs you out of everywhere for no benefit, since the malformed cookie belongs to the site returning the error.

What is the difference between 404 and 400?

A 404 means the address does not exist; a 400 means the request could not be understood. The 404 is about what you asked for, the 400 is about how you asked. That is why the fixes are completely different: one is a URL problem and the other is usually a cookie problem.

404, 400 and the errors people confuse with them
CodeNameWhat it actually meansUsual fix
400Bad RequestThe server could not parse your requestPrivate window, then clear that site’s cookies
401UnauthorizedAuthentication is required and was not suppliedSign in
403ForbiddenThe server understood but refuses to serve itCheck permissions or sign in as the right user
404Not FoundNo resource exists at that addressCheck the URL; search the site; the owner should redirect
410GoneDeliberately removed and not coming backNothing; this is intentional
500Internal Server ErrorSomething failed on the serverNothing from your side; report it
502Bad GatewayA server upstream returned an invalid responseWait and retry; report it if persistent
503Service UnavailableThe server is overloaded or in maintenanceWait and retry
504Gateway TimeoutAn upstream server did not respond in timeWait and retry

The important reading of that table: only the first and fourth rows are frequently fixable by the person seeing them. Everything from 500 downward is a server-side condition, and no amount of clearing cookies will change it.

The error codes people confuse, compared
The 400 row is the useful one: it is the error most likely to be caused on your side and the one most likely to be fixable in under a minute, usually by clearing that site’s cookies.

The chart makes the same point visually. The 400 row scores highest on ‘fixable by you’ and lowest on SEO impact, which is why a 400 is annoying rather than serious. The 404 row is the reverse: harder to fix from the browser, and materially worse for a site if it replaces something that ranked.

What is a 404 bad gateway?

It is a conflation of two separate errors, and if you saw that phrase you almost certainly received one or the other rather than both. A 404 Not Found means the page does not exist. A 502 Bad Gateway means a server acting as a gateway received an invalid response from an upstream server. They come from different layers and have different fixes.

Check the actual status by opening the browser’s developer tools, selecting the network tab, and reloading. The status column shows the real code. This matters because a 502 usually resolves itself and a 404 usually does not.

If it really is a 502

Wait a minute and retry, because 502s are frequently transient. If it persists across several minutes and several pages, the site has an infrastructure problem and the only useful action is reporting it. Nothing on your device will change the outcome.

If it is a 404 after all

Then follow the 404 steps: check the URL, load the domain alone, search the site for the page, and report the broken link to the owner with the exact address and where you found it.

How to fix a 404 or 400 error, in order
Step three resolves a surprising share of 400 errors on its own, because it bypasses the cookies and cached redirects that cause most malformed requests from a browser.

The sequence above is ordered by cost rather than by likelihood, which is why it starts with re-reading the address. The first three steps take under a minute between them and resolve the large majority of cases without anybody else being involved.

1 — Check the address first. Most 404s are typos or truncated pastes..
2 — Load the domain alone. If it works, the path is the problem..
3 — Use a private window. Bypasses cookies and cached redirects..
4 — Clear that site's cookies. The classic cause of a browser-side 400..
5 — Search the site. The page may have moved, not gone..
6 — Report it with the exact URL. Owners cannot fix what they cannot reproduce..

For site owners: what to do about your own 404s

Redirect what had value, return 410 for what was retired deliberately, and repair the internal links that pointed at the dead address. Redirecting everything to the homepage is the common shortcut and it is worse than leaving the 404 in place.

For site owners: which broken URLs to fix first
The top right is where an hour of work returns the most: pages that carried traffic and links and can be redirected in minutes. Genuinely retired pages in the bottom left should return 410 rather than be redirected somewhere irrelevant.

The quadrant chart sets the priority. Old pages that carried traffic and backlinks sit top right — high value, easy fix — and should be redirected first. Genuinely retired pages sit bottom left and should return 410 rather than be pointed at something irrelevant.

How often each cause turns up when a 404 is investigated
Six of the seven causes are inside the site owner’s control, and the top two are found by crawling your own site rather than by waiting for somebody to report a problem.

What that ordering shows is that six of the seven common causes are inside your own control, and the top two are found by crawling your own site rather than by waiting for a visitor to complain. A crawl is the highest-return hour available to most site owners.

A 404 audit that takes an afternoon
Step six is the one that gets skipped. A redirect makes the symptom disappear while the broken internal link stays in the page, which means the next crawl finds it again.

Why blanket redirects to the homepage are wrong

Because a redirect from a specific product page to a homepage is, from a search engine’s point of view, a soft 404: the destination does not fulfill the request. It also frustrates the visitor, who now has to search for what they wanted. Redirect to the closest genuine equivalent or return 404 or 410 honestly.

A 404 triage table for site owners
SignalThreshold that makes it urgentAction
Organic sessions to the old URLAny measurable traffic301 to the closest equivalent today
Referring domains to the old URLOne or more301 to preserve the link value
Internal links pointing at itAnyFix the links in the source pages
Appears in Search Console coverageRepeatedly across weeksInvestigate; it is being crawled for a reason
Only found by a crawlerNo traffic, no linksLow priority; 410 if retired deliberately
Random bot-generated addressNever existedIgnore; 404 is correct

Use the top three rows as a work queue and ignore the bottom one entirely. Sites accumulate 404s from automated scanning that never existed and never mattered, and treating those as work wastes the hour that should go to the first three rows.

When to use 410 instead of 404

When you removed the page deliberately and nothing replaces it. A 410 Gone states that the removal was intentional and permanent, which is a clearer signal than 404 and typically leads to faster de-indexing. For a discontinued product with no successor, 410 is usually the honest answer.

A redirect makes the error disappear while the broken internal link stays in the page. The next crawl finds it again, and over years a site accumulates chains of redirects that slow everything down. Repair the link in the source page as well as adding the redirect.

A — 301 for moved. Permanent move, passes signals to the new URL..
B — 302 for temporary. Use it only when the move really is temporary..
C — 404 for missing. Honest when nothing replaced the page..
D — 410 for gone. Clearer than 404 when removal was deliberate..
E — Never blanket-redirect. Sending everything to the homepage helps nobody..
F — Fix the link too. A redirect patches the symptom, not the cause..

Does a 404 hurt your search rankings?

Only when it replaces a page that had traffic or inbound links. A 404 for something that never existed costs nothing. A 404 on a page that ranked and had links wastes both, and that is the case worth fixing quickly.

404s and search: what matters and what does not
SituationDoes it hurt?What to do
404 on a URL that never existedNoNothing
404 on a page with no traffic and no linksNegligibleLeave it, or return 410
404 on a page that rankedYes301 to the closest equivalent, quickly
404 on a page with external backlinksYes301 to preserve the link value
Many internal links pointing at 404sYes, indirectlyFix the links; it wastes crawl effort
A custom 404 page with helpful navigationNo effect on the codeGood for people; does not change the status
Soft 404: a 200 status on a ‘not found’ pageYesReturn a real 404 or 410 status

The last row is the one people get wrong most often. A page that says ‘not found’ while returning a 200 status tells search engines the content is real, which is worse than an honest 404 because it invites indexing of an empty page.

What to return in each situation
SituationCorrect responseWhy not the alternative
Page moved to a new address301 to the new addressA 404 wastes the traffic and the links
Product discontinued, successor exists301 to the successorVisitors want the replacement
Product discontinued, no successor410 GoneA redirect to a category is a soft 404
Temporary outage on one page503 with a retry hintA 404 tells search engines it is gone
Content moved temporarily302A 301 tells search engines the move is permanent
Address never existed404Nothing else is honest
Campaign URL expired410 or 301 to the evergreen pageDepends on whether a successor exists

The pattern in that table is that the right answer is almost always the one that describes reality most accurately. Search engines and visitors both behave better when the status code is honest than when it is optimized.

Custom 404 pages are for people, not for search engines

A good 404 page explains what happened in plain language, offers site search, and links to the main sections. It does not change the status code and it should not pretend the page exists. Its job is to keep a visitor on the site rather than to influence anything technical.

Is a 404 bad for SEO? — Q. Only when it replaces a page that had traffic or links..
Should I redirect every 404? — Q. No. Redirect what had value; 410 the rest..
Why do I get 400 on one site only? — Q. Almost always that site's cookies..
What is a 404 bad gateway? — Q. Two different errors; check which you actually got..
Does a custom 404 page help? — Q. Yes, for people. It does not change the status code..
How fast do errors clear? — Q. Days to weeks after the fix, on recrawl..

How to prevent 404s in the first place

Decide URL structure once, redirect whenever anything moves, crawl regularly, and treat discontinued content as a decision rather than a deletion. Most 404s on established sites come from a migration where the redirect map was an afterthought.

  1. Choose a URL pattern at the start and do not change it for cosmetic reasons.
  2. Whenever a page moves, create the 301 redirect in the same change, not later.
  3. Before any replatform, export every URL with its traffic and map every one.
  4. Crawl the site monthly and fix internal links pointing at dead addresses.
  5. Check Search Console coverage reports rather than waiting for complaints.
  6. Have a written rule for what happens to discontinued products and expired pages.
  7. Keep redirect chains short: point old URLs at the final destination, not at another redirect.

Rule seven quietly matters. Chains of redirects accumulate over years, slow every request through them, and occasionally break entirely when an intermediate step is removed. Repointing old URLs directly at the current destination is maintenance worth doing annually.

If you are planning a site move, our web design and development page and ecommerce development page both cover the migration planning that prevents this category of problem entirely.

Error pages on your own site: a five-minute check

Type a deliberately wrong address on your own domain and look at three things: what the page says, whether it offers a route onward, and what status code it returns. Most sites fail at least one of the three, and all three are cheap to fix.

What to check on your own error page
CheckHowFailing looks like
The status codeDeveloper tools, network tab, reload200 OK on a not-found page
The messageRead it as a stranger wouldTechnical jargon or a bare error number
The route onwardLook for search and main navigationA dead end with a back button
BrandingDoes it look like your site?A default server page from the host
LoggingAsk whether 404s are recorded anywhereNobody finds out until a customer complains
MobileLoad it on a phoneUnstyled or unreadable

The first row is the one that matters technically and the third is the one that matters commercially. A helpful error page keeps a visitor who would otherwise leave, and an honest status code keeps search engines from indexing an empty page.

Losing traffic after a site change?

Broken redirects and unmapped URLs are the most common cause, and they are usually fixable. We can audit what happened and tell you what is recoverable.

Talk to Progression Agency

Web platform, performance and search talks from the platform publishers

Publicly available sessions on the web platform, performance and search. None of these are ours; each is credited to its channel and upload date, every identifier was checked live before publication, and each tile loads its player only when clicked.

Websites and design

Frequently asked questions

What does HTTP 404 mean?
The server received and understood your request and there is no resource at that address. The request was valid; the address was not. It does not mean the site is down — load the domain on its own to confirm that.
What does 400 Bad Request mean?
The server could not understand the request. Something your browser sent was malformed: the URL syntax, a header, or most commonly a cookie for that site that has grown too large. Unlike a 404 this is frequently caused on your side and fixable in under a minute.
What is the difference between 404 and 400?
A 404 is about what you asked for — nothing exists at that address. A 400 is about how you asked — the request itself could not be parsed. That is why the fixes differ completely: one is a URL problem, the other is usually a cookie problem.
How do I fix a 400 Bad Request?
Open the same URL in a private window. If it loads, clear the cookies and site data for that one site, then reload. If it still fails, retype the URL by hand rather than pasting it, in case a stray character or line break came with the paste.
Why does clearing cookies fix a 400 error?
Because the most common browser-side cause is an oversized or corrupted cookie for that site, which makes the request header too large or malformed for the server to parse. Clearing cookies for that one site removes the offending data without logging you out of everywhere else.
Should I clear all my cookies?
No. Clear them for the single site returning the error. The malformed cookie belongs to that site, and clearing everything logs you out of every service you use for no additional benefit.
What is a 404 bad gateway?
It is two different errors conflated. A 404 Not Found means the page does not exist; a 502 Bad Gateway means a server acting as a gateway received an invalid response from upstream. Check the real status in your browser’s network tab, because a 502 usually resolves itself and a 404 does not.
What is a 502 Bad Gateway and can I fix it?
It means one server got an invalid response from another server it depends on. There is nothing you can do from your side. Wait a minute and retry, since 502s are often transient; if it persists across pages and minutes, report it to the site.
How do I know which error I actually received?
Open your browser’s developer tools, select the network tab, and reload the page. The status column shows the real HTTP code. This takes fifteen seconds and prevents you troubleshooting the wrong problem entirely.
What is the difference between 403 and 404?
A 403 Forbidden means the resource exists but the server refuses to serve it to you — usually a permissions issue. A 404 means it does not exist at all. If you should have access, sign in or check you are using the right account.
What is the difference between 404 and 410?
A 404 says nothing is there. A 410 Gone says it was removed deliberately and permanently. The 410 is a clearer signal and typically results in faster removal from search results, which makes it the honest choice for content you retired on purpose.
Is a 404 bad for SEO?
Only when it replaces a page that had traffic or inbound links. A 404 for something that never existed costs nothing at all. The damaging case is a page that ranked or attracted links now returning nothing, which wastes both.
Should I redirect every 404 to my homepage?
No. A redirect from a specific page to a homepage is treated as a soft 404 because the destination does not fulfill the request, and it frustrates visitors who now have to search again. Redirect to the closest genuine equivalent or return an honest 404 or 410.
What is a soft 404?
A page that says ‘not found’ while returning a 200 OK status. It tells search engines the content is real, which invites indexing of an empty page. It is worse than an honest 404 and is a common misconfiguration on custom error pages.
Does a custom 404 page help my SEO?
No, and that is not its job. It does not change the status code. Its purpose is to keep a visitor on the site by explaining what happened, offering search and linking to the main sections. Do that well and do not pretend the page exists.
How do I find all the 404s on my site?
Two sources. Search Console’s coverage and crawl reports show what search engines encountered, including referring pages where available. A site crawler shows internal links pointing at dead URLs, which is the largest single cause and the one you can fix immediately.
Which 404s should I fix first?
The ones with traffic and inbound links, because those are wasting something measurable. Sort your list by traffic and by referring domains rather than working through it alphabetically.
Should I fix the internal link or just add a redirect?
Both. A redirect makes the error disappear while the broken link remains in the page, so the next crawl finds it again and redirect chains accumulate over the years. Repair the link in the source page as well.
What causes most 404s on an established site?
Internal links pointing at old URLs, and pages renamed without a redirect. Both are inside your control and both are found by crawling your own site rather than waiting for somebody to report a problem.
How do I stop a site migration creating 404s?
Export every existing URL with its traffic before anything changes, map each one to a new address or retire it deliberately, implement the 301 redirects before launch, and verify them live on launch day. Deferring the redirect map is where migration traffic is lost.
How long do redirect chains matter?
They slow every request that passes through them and occasionally break when an intermediate step is removed. Repointing old URLs directly at the current destination is worth doing annually on any site that has moved things more than once.
Can a browser extension cause a 400 error?
Yes. An extension that adds to request headers can make them too large for a server to accept. Testing in a private window with extensions disabled is the quickest way to identify this, which is why it is step one in the fix sequence.
Why does a URL work for someone else but not for me?
Almost always local state: a cookie, a cached redirect or a browser extension. A private window isolates all three at once, which is why it is the single most useful diagnostic step for any error that appears to be personal to you.
What should I include when reporting a broken link to a site owner?
The exact URL that failed, the page you followed the link from, the error code you actually received, and roughly when. Owners cannot fix what they cannot reproduce, and ‘a page on your site is broken’ is not reproducible.

Sources and further reading

  1. Google Search Essentials — SEO starter guide
  2. Google: creating helpful, reliable, people-first content
  3. Google: intro to structured data
  4. Google: LocalBusiness structured data
  5. Google: FAQPage structured data
  6. Google: Article structured data
  7. Google: Product structured data
  8. Google: title links in search results
  9. Google: control your snippets
  10. Google: robots.txt introduction
  11. Google: sitemaps overview
  12. Google: consolidate duplicate URLs
  13. Google: redirects and Search
  14. Google: JavaScript SEO basics
  15. Google: multi-regional and multilingual sites
  16. Google Search Central Blog
  17. Google: get started with Search Console
  18. Google: how local search results are determined
  19. Google Business Profile: prohibited and restricted content
  20. Google Business Profile: address and service area guidelines
  21. Google Business Profile: review policy
  22. Google Business Profile: add or edit categories
  23. Google Ads: location targeting settings
  24. Google Ads: about negative keywords
  25. Google Ads: about Quality Score
  26. Google Ads: importing offline conversions
  27. Google Ads: about Smart Bidding
  28. Google Ads: about Performance Max
  29. Google Local Services Ads: eligibility and screening
  30. Google Ads: keyword match types
  31. Google Analytics 4: about conversions
  32. Google Analytics 4: attribution models
  33. US Census Bureau QuickFacts: New Jersey
  34. US Census Bureau: American Community Survey
  35. US Census: Statistics of US Businesses
  36. Bureau of Labor Statistics: New Jersey data
  37. BLS: Occupational Employment and Wage Statistics
  38. NJ Department of Labor: labor market information
  39. New Jersey Business Action Center
  40. US Small Business Administration: New Jersey district
  41. USA.gov: business resources
  42. web.dev: Core Web Vitals explained
  43. web.dev: Largest Contentful Paint
  44. web.dev: Cumulative Layout Shift
  45. web.dev: Interaction to Next Paint
  46. Google PageSpeed Insights
  47. Google Rich Results Test
  48. Google Search Console
  49. W3C Markup Validation Service
  50. Schema.org: LocalBusiness type
  51. Schema.org: Service type
  52. Schema.org: FAQPage type
  53. Schema.org: HowTo type
  54. W3C: WCAG 2.2 quick reference
  55. FTC: CAN-SPAM Act compliance guide
  56. FCC: telemarketing and robocall rules (TCPA)
  57. FTC endorsement guides — reviews and testimonials
  58. FTC: rule on consumer reviews and testimonials
  59. HHS: HIPAA guidance on online tracking technologies
  60. New Jersey Courts: attorney advertising guidelines
  61. New Jersey DCA: construction codes and permits
  62. New Jersey Home Improvement Contractor registration
  63. New Jersey Division of Consumer Affairs
  64. TikTok for Business
  65. TikTok Creative Center
  66. TikTok Ads Help Center
  67. TikTok Community Guidelines
  68. TikTok Terms of Service
  69. TikTok Privacy Policy
  70. TikTok Safety Center
  71. TikTok Transparency Center
  72. TikTok Creator Portal
  73. TikTok Newsroom
  74. TikTok for Developers
  75. TikTok advertising solutions
  76. TikTok Creator Marketplace
  77. TikTok Business Center
  78. TikTok for Business blog
  79. TikTok Creative Center: top ads
  80. TikTok Branded Content policy
  81. TikTok Shop for sellers
  82. Instagram for Business
  83. Instagram for Creators
  84. Instagram Help Center
  85. About Instagram
  86. Meta Business Suite
  87. Meta Business Help Center
  88. Meta Transparency Center
  89. About Meta
  90. Meta: Instagram platform docs
  91. YouTube Creators
  92. YouTube Official Blog
  93. YouTube Shorts help
  94. How YouTube Works
  95. YouTube Studio
  96. LinkedIn Marketing Solutions
  97. LinkedIn Help
  98. Pinterest Business
  99. Pinterest Business Help
  100. Snapchat for Business
  101. X for Business
  102. Reddit communities
  103. Reddit for Business Help
  104. ASCAP
  105. BMI
  106. SESAC
  107. Global Music Rights
  108. PRS for Music (UK)
  109. PPL (UK)
  110. SOCAN (Canada)
  111. APRA AMCOS (Australia)
  112. GEMA (Germany)
  113. SACEM (France)
  114. SIAE (Italy)
  115. JASRAC (Japan)
  116. IFPI
  117. RIAA
  118. National Music Publishers Association
  119. Harry Fox Agency
  120. SoundExchange
  121. Music Reports
  122. Epidemic Sound
  123. Artlist
  124. Soundstripe
  125. PremiumBeat
  126. AudioJungle
  127. Free Music Archive
  128. Creative Commons
  129. Incompetech
  130. FTC: advertising and marketing
  131. FTC: disclosures 101
  132. FTC: endorsement guides
  133. FTC: consumer reviews rule
  134. FTC: advertising FAQs
  135. US Copyright Office
  136. US Copyright Office: DMCA
  137. US Copyright Office: music FAQ
  138. US Copyright Office: fair use FAQ
  139. USPTO: trademarks
  140. UK Advertising Standards Authority
  141. ACCC (Australia)
  142. Competition Bureau Canada
  143. GDPR overview
  144. California Consumer Privacy Act
  145. COPPA
  146. FTC: children’s privacy
  147. W3C Web Accessibility Initiative
  148. W3C: WCAG
  149. W3C: captions
  150. W3C: making audio and video accessible
  151. ADA.gov
  152. WebAIM
  153. Epilepsy Foundation
  154. Pew Research: internet and technology
  155. DataReportal
  156. US Census Bureau
  157. US Bureau of Labor Statistics
  158. Interactive Advertising Bureau
  159. Think with Google
  160. Google Trends
  161. Nielsen insights
  162. Schema.org: VideoObject
  163. Schema.org: SocialMediaPosting
  164. Schema.org: MusicRecording
  165. Schema.org: HowTo
  166. Schema.org: FAQPage
  167. Schema.org: Organization
  168. Google: video best practices
  169. Google: video structured data
  170. CapCut
  171. Adobe Premiere Rush
  172. DaVinci Resolve
  173. Canva
  174. Descript
  175. VEED
  176. Kapwing
  177. Otter.ai
  178. Later
  179. Buffer
  180. Hootsuite
  181. Sprout Social
  182. Google Analytics
  183. Google Search Console
  184. Google Analytics developer docs
  185. GA4: events and conversions
  186. Matomo
  187. Plausible Analytics
  188. Similarweb
  189. UK Information Commissioner’s Office
  190. Office of the Privacy Commissioner of Canada
  191. Australian OAIC
  192. European Data Protection Board
  193. EU data protection
  194. EU Digital Services Act
  195. Ofcom
  196. FCC
  197. AIGA
  198. Nielsen Norman Group
  199. Smashing Magazine
  200. web.dev
  201. MDN: web media
  202. MDN: the video element
  203. ISO 21001 (reference)
  204. Buma/Stemra (Netherlands)
  205. STIM (Sweden)
  206. Teosto (Finland)
  207. Koda (Denmark)
  208. TONO (Norway)
  209. IMRO (Ireland)
  210. SGAE (Spain)
  211. ZAiKS (Poland)
  212. KOMCA (South Korea)
  213. MCSC (China)
  214. CISAC
  215. World Intellectual Property Organization
  216. TikTok: creating videos
  217. TikTok: exploring videos
  218. TikTok: privacy settings
  219. TikTok: growing your audience
  220. TikTok Creator Academy
  221. TikTok Effect House
  222. TikTok for small business
  223. Instagram: Reels help
  224. YouTube: Shorts best practice
  225. How YouTube recommends
  226. Pinterest Predicts
  227. Snapchat for Business
  228. Hootsuite blog
  229. Social Media Examiner
  230. Marketing Week
  231. Adweek
  232. MDN — 404 Not Found
  233. MDN — 400 Bad Request
  234. MDN — 502 Bad Gateway
  235. MDN — 410 Gone
  236. Google — redirects and site moves
  237. RFC 9110 — HTTP Semantics

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.