Turning an established audience
into a managed digital presence.

The owner’s challenge and my contribution

SigmaMyself was a unique opportunity to help an owner with an established client base who was not deeply technical and found it difficult to manage the digital side of the business. I handled website creation and management, built the digital presence, and managed SEO.

The challenge was to make publishing and maintenance predictable while preserving discoverability. A visually polished site is only part of that work. Content structure, URL stability, indexability, internal navigation, and operational checks determine whether the platform remains useful as it grows.

The technology framework

The source repository documents a migration from Wix to a static Astro site. Articles live in MDX content collections with schema-validated frontmatter. Tailwind and custom styling support presentation; Astro generates public HTML at build time. Cloudflare Pages serves the static output.

The dependency manifest includes a Cloudflare adapter, but the documented deployment is a static build that does not require that adapter at runtime. Article content and metadata are version controlled, and the build produces the routes, XML sitemap, RSS feed, headers, and redirects used in deployment.

Content contracts and predictable publishing

A content schema enforces title and description lengths, publication dates, optional update dates, categories, canonical paths, source URLs, and draft state. This converts incomplete metadata into an explicit build problem rather than silently publishing a malformed page.

Illustrative, simplified code explaining the implementation pattern. This is not a copy of private production source.

// Simplified representation of the repository's article schema.
const articleSchema = z.object({
  title: z.string().min(10).max(120),
  description: z.string().min(50).max(200),
  pubDate: z.coerce.date(),
  updatedDate: z.coerce.date().optional(),
  categories: z.array(z.string()).default([]),
  canonicalPath: z.string().startsWith("/post/"),
  originalUrl: z.url(),
  draft: z.boolean().default(false)
});

Templates consume the same metadata for page headings, article cards, canonical URLs, social previews, and structured data. A single content contract reduces inconsistencies between the visible article and the metadata a crawler receives. Draft filtering must apply to archives and feeds as well as individual article routes.

Migration without discarding existing URLs

The repository preserves the existing Wix /post/... URL structure and retains migration inventories and raw backups. A migration needs a mapping from each old URL to its intended destination, with explicit permanent redirects for changed routes and no broad redirect that hides lost content.

Before cutover, the documented process compares backed-up URLs, metadata, images, internal links, and redirects. Hostname canonicalization sends the apex host to the chosen www host. Canonical tags, sitemap entries, redirect destinations, and internal links must agree to avoid fragmented URL signals.

Illustrative, simplified code explaining the implementation pattern. This is not a copy of private production source.

// Illustrative migration validation contract.
for (const entry of migrationInventory) {
  const page = await inspectBuiltRoute(entry.destination);
  assert(page.status === 200);
  assert(page.canonical === canonicalOrigin + entry.destination);
  assert(page.title.length > 0);
  assert(!page.robots.includes("noindex"));
  if (entry.sourcePath !== entry.destination) {
    assertRedirect(entry.sourcePath, entry.destination, 301);
  }
}

Technical SEO as a maintained system

SEO metadata is generated through a shared component. The stack supplies XML sitemaps, an RSS feed, robots discovery, article date metadata, and social tags. The build includes redirect generation, and separate validation tooling checks emitted output.

Content architecture groups material into meaningful categories and pillars so navigation and internal links communicate topic relationships. Performance work favors pre-rendered content and targeted browser behavior instead of hydrating the entire page. Accessibility checks use Playwright and axe-core alongside layout and interaction audits.

SEO work also requires monitoring the outcome after deployment: crawl errors, index coverage, landing-page traffic, search impressions, and conversion events. Traffic and sales attribution need defined channels, reporting windows, and conversion semantics; pageviews alone cannot establish revenue.

Reducing the management burden

The site includes browser-based planning tools, including a weekly reset planner with local persistence and validated JSON import/export. The documented workflow tests persistence, priority limits, printing, mobile width, and carry-forward behavior. That makes the digital presence more useful than a collection of static promotional pages.

The owner’s management challenge informed the architecture: consistent templates, schema-backed content, reproducible builds, and explicit maintenance checks. Those mechanisms reduce the number of technical decisions needed for each content update.

Business impact

I report that the website now generates over $25,000 per month from the traffic I brought in. The figure is a project outcome supplied from my experience; the public site and source code establish the platform and technical process, not the underlying sales ledger. My contribution combined website creation, ongoing management, and SEO to give the owner a durable channel for reaching clients.