Before You Go Live

October 4, 2025

While working on the Fujifilm Pharmaceuticals U.S.A., Inc website, I ran into a common issue—there wasn’t enough time allocated for critical pre-launch work. Before hitting “Go Live,” steps like compliance and marketing readiness are essential.

Compliance Pages

Compliance pages are dedicated sections on a website that explain how the organization meets legal, regulatory, and industry requirements related to privacy, accessibility, and data usage.

They typically include things like:

• Privacy Policy (how user data is collected, used, and shared)

• Cookie Policy (what tracking technologies are used and why)

• Terms of Use (rules for using the site or service)

• Accessibility Statement (how the site supports users with disabilities, often aligned with standards like WCAG)

In regulated industries (like pharma or healthcare), these pages often also include additional disclosures required by frameworks such as the General Data Protection Regulation or the California Consumer Privacy Act.

Accessibility

Accessibility in web development means designing and building websites so that everyone can use them, including people with disabilities (visual, auditory, motor, or cognitive).

This includes things like:

• Screen reader support for visually impaired users

• Keyboard navigation for users who can’t use a mouse

• Proper color contrast for readability

• Clear structure with headings and semantic HTML

• Text alternatives for images (alt text) and media

Most accessibility standards are guided by the WCAG (Web Content Accessibility Guidelines), which outlines how to make digital content more usable and perceivable for all users.

It’s also one of the highest legal risk areas for websites—especially in B2C and e-commerce—where accessibility-related lawsuits have become increasingly common under frameworks tied to the ADA (Americans with Disabilities Act).

Privacy Consent

Privacy consent means users must be informed and give permission before their data (like cookies or tracking) is used—especially under laws like the GDPR (General Data Protection Regulation) and CCPA (California Consumer Privacy) Act, along with other local and national regulations depending on where your users are located.

OneTrust helps manage this, but it still needs to be properly implemented on your site. It:

• Shows a cookie consent banner

• Lets users accept or customize tracking

• Blocks non-essential scripts until consent is given

• Stores consent choices for compliance

Privacy regulation is evolving rapidly, with an increasing number of U.S. states adopting privacy laws that mirror or even exceed existing standards like the California Consumer Privacy Act. Practices that were once standard—such as default or implied consent—are shifting toward stricter requirements, with opt-in consent becoming more common, particularly as wiretapping-related laws such as the CIPA (California Invasion of Privacy Act) and other digital privacy frameworks reshape how tracking technologies must be handled.

Security Infrastructure Layers

The security infrastructure layers focus on protecting a website and its users at the network and application level, not just the data itself.

Modern web platforms typically rely on a combination of WAF, CDN, and edge services to reduce risk and improve resilience:

• A WAF (Web Application Firewall) helps filter and block malicious traffic such as SQL injection, bot attacks, and common exploit patterns before they reach the application.

• A CDN (Content Delivery Network) improves performance by caching content closer to users globally, while also helping absorb traffic spikes and mitigate DDoS attacks.

• Edge services extend security and logic closer to the user, enabling faster request handling, geo-based controls, bot protection, and early threat detection before traffic hits core infrastructure.

Together, these layers create a distributed security perimeter that reduces exposure, improves reliability, and strengthens protection against both automated attacks and targeted threats.

Marketing & SEO

Marketing & SEO ensure a website is discoverable, measurable, and aligned with business goals once it goes live.

This typically includes:

• Implementing metadata (titles, descriptions, Open Graph tags) for search and social sharing

• Structuring content with proper headings and semantic HTML for search engines

• Setting up analytics and tagging (e.g., tracking conversions, campaigns, and user behavior)

• Configuring search engine indexing rules (sitemaps, robots.txt)

• Ensuring performance and Core Web Vitals are optimized, since speed impacts rankings

It also involves making sure marketing tools (like analytics, pixels, and tag managers) are properly implemented and only fire in compliance with privacy consent rules where required.

In short, SEO and marketing readiness ensure the site isn’t just live—it’s visible, measurable, and ready to perform.

Ongoing Maintenance

Ongoing Maintenance refers to the continuous work required after a website goes live to keep it secure, stable, and up to date.

This typically includes:

• Applying security patches and dependency updates

• Monitoring uptime, performance, and error logs

• Fixing bugs and addressing production issues

• Updating content, components, and integrations as needed

• Ensuring compliance tools, analytics, and tracking remain functional as regulations and requirements change

• Enabling and managing automatic updates for CMS core, plugins, and themes

It must be explicitly accounted for in the launch and project plan—because if it’s not, systems can quickly drift out of date and introduce security vulnerabilities, compatibility issues, and compliance gaps over time.

Health Screen check

You should check the CMS health screen (such as WordPress Site Health) before going live. It helps surface issues that can impact stability, security, and performance.

It typically highlights:

• Outdated plugins, themes, or core versions

• Security configuration issues

• REST API or background task failures

• Server environment compatibility (PHP version, database, etc.)

• Performance and caching recommendations

In practice, it acts as a built-in diagnostic tool that helps catch risks early—before they become production issues.