Launching a Website in Seattle: The Sequence, the Checks, and the Month After
A practical launch and aftercare plan for Seattle businesses, covering Washington tax rules, state privacy law, accessibility deadlines and what has to keep running after go-live.
Most Seattle website projects do not fail in the design phase. They fail in the fortnight either side of go-live, when nobody wrote down who flips DNS, who checks the forms, who tells finance the invoice line is now taxable, and who is still looking at the site ninety days later. Here is the sequence, the Washington State checks, and the work that has to keep happening after launch.
Sort the tax question before you sign anything
Most Seattle buyers have not absorbed this change. Washington's ESSB 5814 took effect on 1 October 2025 and made advertising services and custom website development services retail sales, subject to retail sales tax and the retailing B&O classification rather than the old service classification. The Department of Revenue has published separate interim guidance for custom website development and advertising services. It is still interim, which means it can move.
So your build quote may now carry sales tax at the Seattle combined rate, which sits at 10.55 percent in 2026 after King County and the city each added a tenth of a point in January. Ask your vendor to show the tax as a separate line, ask your accountant whether it is a purchase for resale in your case, and do not assume a vendor outside Washington makes it disappear, because use tax exists.
Seattle's own business licence tax also changed on 1 January 2026. Proposition 2 raised the gross receipts threshold from 100,000 dollars to 2 million dollars and added a matching standard deduction, while raising rates above that line. If the new site will sell into other cities, model the apportionment before launch.
The pre-launch sequence
Run these in order. Each is cheap now and expensive later.
- 01Freeze the content. Not the design, the copy. Page seven with no copy is the most common reason a Seattle launch slips past a quarter end.
- 02Map every old URL to a new one. Write the redirect list as a spreadsheet a human can read, then implement it.
- 03Stage on a real URL with real data. Lorem ipsum tests nothing. Load the actual products, team bios and PDF spec sheets.
- 04Test forms end to end, including the CRM. Submit as a customer, then check the record landed with the right owner and source.
- 05Run the legal and accessibility checks below. These generate letters rather than complaints.
- 06Agree the rollback. Who decides, and how long it takes.
The Washington checks that actually bite
Consumer health data, even if you are not a healthcare business
The My Health My Data Act is the sharpest privacy statute your site is likely to touch in Washington, and its definition of consumer health data reaches far past hospitals: fitness tracking, supplements, mental wellness, reproductive care, gender affirming care, biometrics and diagnoses. If any of that applies, the act requires a separate and distinct consumer health data privacy policy, linked prominently from your homepage, containing only what the act requires and no marketing language. Opt in consent is needed before collection and sharing, and written authorisation before any sale.
What sets it apart from most US privacy law is the private right of action through Washington's Consumer Protection Act. That means plaintiffs, not just the Attorney General. For a Seattle wellness studio, supplement brand, telehealth startup or South Lake Union life sciences company, this belongs on the launch list, not a later phase.
Email and SMS, before you connect the marketing automation
Washington's Commercial Electronic Mail Act, chapter 19.190 RCW, is stricter than the federal CAN-SPAM baseline and carries damages of 500 dollars per message or actual damages, whichever is greater, with no need to prove harm. Washington courts have read the subject line prohibition broadly, so a misleading Re: sent to a Washington recipient is real exposure. The text provision is tighter still, barring commercial texts to numbers assigned to Washington residents outside narrow exceptions.
So at launch, check that your newsletter double opt in genuinely double opts in, that unsubscribe works on the first click, that SMS consent sits on its own checkbox and is logged with a timestamp, and that nobody imported a purchased list during migration.
Accessibility, with a real deadline if you sell to the public sector
If your customers include the City of Seattle, King County, Sound Transit, Washington State agencies or the University of Washington, the Department of Justice Title II rule applies to them and flows downhill to you. After the April 2026 interim final rule extended the dates, entities serving 50,000 or more people must meet WCAG 2.1 Level AA by 26 April 2027, and smaller entities and special districts by 26 April 2028. Procurement teams already ask for conformance documentation, so build to that standard now and write the accessibility statement at launch.
Language, based on who actually lives here
Seattle's top languages reporting puts Spanish, Chinese, Vietnamese and Somali at the front, and Seattle Public Schools translates into Amharic, Chinese, Somali, Spanish and Vietnamese. If you serve consumers in Rainier Valley, Beacon Hill, White Center or Delridge, an English only site leaves money behind. Start with the two or three pages that carry the transaction, have people translate them rather than a plugin, and mark them up with correct hreflang.
Checkout and tax, if you sell anything
Washington uses destination based sourcing, so tax is calculated on the buyer's delivery address, not your office. Rates vary across King, Snohomish and Pierce counties, so address level rate lookup at checkout is not optional. Test Seattle, Bellevue, Tacoma and an unincorporated King County address before launch. For remote sellers the economic nexus threshold is 100,000 dollars in Washington sourced gross retail sales in the current or prior calendar year, and marketplace sales count toward it.
Launch day, in Pacific time
Seattle runs on Pacific Time, and the useful cutover window is early morning, before the Amazon, Boeing and Alaska Airlines supplier world starts sending enquiries. FuturByte works from Dubai, eleven hours ahead, so our late afternoon is your start of day. Migration happens while Seattle sleeps, and the handover is live at around 8am Pacific rather than an email you read at noon.
Set DNS TTL to 300 seconds the day before and keep the old host running a week. Once the switch is made, walk the conversion path on a phone over cellular, because office wifi in a Pioneer Square building tells you nothing about a contractor checking your site from a job site in Kent.
The first thirty days
- Day one to three: watch Search Console for coverage errors and 404 spikes. A redirect list is never complete on the first pass.
- Day three: confirm every launch day form submission reached a human. Check spam folders, not just the CRM.
- Week one: re-check Core Web Vitals on field data, not a lab score. Passing on a developer machine and failing on real Seattle mobile traffic is not passing.
- Week two: reconcile Google Business Profile with the new site. Hours, service areas, phone number and URL structure all need to match.
- Week four: compare organic traffic and conversion against the same month last year, not launch week. Launch week is noise.
What has to keep happening
Sites decay when the agency relationship ends at launch and nobody internally owns the thing. The monthly rhythm is short: apply security updates, review the top ten landing pages against what people actually searched for, publish something, check that forms still submit. The quarterly rhythm adds the Washington items. Has your product range drifted into consumer health data territory. Has the DOR interim guidance been superseded. Has your accessibility statement gone stale. Has a new city or county rate changed your checkout maths.
Seattle buyers are unusually literate about software. They work at Amazon, Microsoft, Zillow, Expedia, Alaska Airlines, Fred Hutch and a long tail of biotech and marine services firms. A slow site, a broken form or a privacy policy that obviously came from a template gets noticed. That is the real argument for aftercare, more than any compliance deadline.
Before launch, write down the name of the person who will look at this site in ninety days. If that line is blank, the site will decay no matter how well it was built.
If you want a second opinion on the sequence, the tax treatment of the build, or what your aftercare should cover, send us the brief. We will say what we would do differently, including when the answer is that you do not need a rebuild at all.
