SEO/GEO/AEO specialist • Content Writer • Technical Writer•Web2 and Web3

I help brands get found by search engines, and AI.

Illustration of a person writing at a desk

I fix the technical groundwork most sites get wrong, then write the content that earns visibility once it's fixable. That means SEO audits and on-page fixes, developer docs and protocol explainers, research-backed articles, and everything in between - for teams building in web2 and web3.

What to expect

Skills

SEO · GEO · AEO · Keyword Research · On-Page SEO · Off-Page SEO · SEO Content Writing · Content Optimization · Technical Writing

Stack

Ahrefs · Screamingfrog · Ubersuggest · SEMrush · Google Analytics · Google Search Console · Google Tag Manager · Microsoft Clarity · Sanity CMS · Google Docs · Markdown · HTML/CSS/JS

Based in UTC+1, open to remote and contract roles.

Recent proof of work

I took brightjasper.com from unindexed and 33% Ahrefs health score to a 100% Ahrefs health score, then to a Google AI Overview citation - in 72 hours.

Read the case study →

Need a site that's actually found, and writing that makes sense once people get there?

I can help with SEO audits and fixes, technical docs, and editorial or product writing for web2 and web3 products.

Common questions

What does Bright Jasper actually do?

SEO, AEO, and GEO optimization and content writing for brands, plus technical writing for web2 and web3 teams. Work spans keyword research, on-page and technical SEO fixes, developer documentation, research-backed articles, and editorial content.

Does the SEO work include technical fixes, or just content?

Both. That includes metadata, schema markup, canonical and redirect issues, Open Graph setup, and backlink strategy, tracked through Ahrefs, Google Search Console, and Google Analytics - not just keyword-targeted writing.

Can Bright Jasper write about technical or blockchain products?

Yes. Work covers software, developer tools, infrastructure, blockchain, and web3 products, backed by a software engineering background and ongoing Computer Science study.

Who is the writing for?

Developers, technical decision-makers, product users, and broader audiences, depending on the piece. The goal is accuracy without losing the reader.

What makes Bright Jasper's process technical?

Source verification, version-controlled docs-as-code workflows, and familiarity with the systems being written about. Claims are checked against primary sources before publication.