Why I Built an SEO Practice Platform for Aspiring Virtual Assistants

SEO VA Practice project showing simulated SEO assignments and the learning process behind building the Practice Lab.
SEO VA Practice started as an idea for practicing SEO work before handling a real client. Building it is also teaching me how GitHub, Vercel, domains, and web projects fit together.

Aspiring SEO virtual assistants have an awkward problem: they are expected to understand SEO work before they have had a real client to practice with.

Competition for virtual assistant work can also be high. Between January 2025 and July 2026, VA Masters reported processing more than 166,000 applications from Filipino virtual assistants, with roughly one placement for every 508 applicants in its recruitment pipeline.

That statistic describes one recruitment company's data, not the entire Philippine VA industry. Still, it gives some context for how competitive the path into VA work can be.

That is one reason I started building SEO VA Practice, a personal project where people preparing for SEO VA work can complete realistic simulated assignments before handling client work.

Instead of building another collection of SEO lessons, I wanted to create a place where someone could receive an assignment, work with practice data, complete a deliverable, and review the result.

I am also using the project to learn.

My background is in content writing, SEO, and content planning. Building SEO VA Practice has given me a reason to work directly with GitHub, Next.js, Vercel, domains, builds, browser storage, and other technical workflows that I previously understood mostly from the content side.

This is the first article in a series documenting what I am building, what has confused me, and what I am learning along the way.

What Is SEO VA Practice?

SEO VA Practice is a personal project I am building to help aspiring SEO virtual assistants practice realistic SEO tasks before working with a real client.

The Practice Lab uses simulated assignments instead of relying only on lessons or tutorials. Each assignment follows a simple learning flow:

Client Brief → Deliverable → Practice Data → Do the Work → Review

Five-step SEO VA Practice learning flow from client brief to deliverable, practice data, doing the work, and review.
The SEO VA Practice learning flow uses simulated assignments from client brief to review.

A learner starts with a brief, sees what needs to be completed, works with practice data, produces the required deliverable, and then reviews the result.

The assignments are simulated practice exercises. They are not real client projects and should not be presented as professional client experience.

My goal is to make the learning process feel closer to SEO work while giving someone room to practice before working with a client.

What I Was Trying to Build

The idea behind SEO VA Practice came from a gap I kept thinking about.

Someone can read about keyword research, on-page SEO, content briefs, competitor research, technical SEO, and other common SEO tasks. They can also watch tutorials showing how the work is done.

But knowing what a task is and completing it are two different things.

Someone preparing for SEO VA work may understand the theory but still wonder what to do when they are given a brief, a spreadsheet, a website, or a specific deliverable.

That was the gap I wanted SEO VA Practice to address.

I wanted to create a place where someone could practice receiving an assignment, figuring out what is expected, working with realistic practice materials, and completing the task without the pressure of working on a real client account.

The simulated assignments are not meant to look like real client experience. They are a structured way to practice before that first opportunity arrives.

I also wanted the project to stay focused.

Rather than trying to cover every part of SEO at once, I started with two assignments: Local SEO Competitor Research and Keyword Research + Search Intent.

I chose those because both require more than knowing a definition. You have to review information, make decisions, organize your findings, and produce something another person can use.

Here are the first two assignments currently available in the Practice Lab.

SEO VA Practice assignment library showing Local SEO Competitor Research and Keyword Research plus Search Intent.
Early Practice Lab assignments: Local SEO Competitor Research and Keyword Research + Search Intent.

Why I Decided to Build It Myself

I could have stopped at planning the assignments, writing the content, and defining how the Practice Lab should work.

That would have stayed close to the kind of work I already know.

Instead, I decided to use SEO VA Practice to learn more of the technical side too.

My background is in content writing, SEO, and content planning. I am not a software developer, and I did not start this project with a strong background in GitHub, Next.js, Vercel, deployment workflows, or domain configuration.

That was part of the reason I wanted to work on it myself.

I have written about technical products and workflows for years. Working through one when something breaks is a different experience.

With SEO VA Practice, I had a reason to learn by doing.

If I wanted to change a page, I had to find the right file.

If I wanted to publish that change, I had to understand what happened between my local project, GitHub, and Vercel.

If I wanted the marketing site and Practice Lab to use separate domains, I had to work through DNS and custom-domain settings.

I used ChatGPT throughout the process to help me understand unfamiliar commands, errors, warnings, and possible fixes.

I still wanted to know what was changing. I tried to inspect the files, test the result, and understand enough of the workflow before moving on.

That became one of the reasons I kept working on the project myself.

SEO VA Practice was becoming a place for other people to practice SEO work. At the same time, it was giving me a practical reason to become more comfortable with the technical systems behind a website.

From an Idea to Two Working Websites

As the project took shape, it became clear that I was building two separate parts.

The first is the main website at seovapractice.com ↗.

This is where I explain what SEO VA Practice is, who it is for, and how the practice approach works.

The second is the Practice Lab at app.seovapractice.com ↗.

This is where the simulated assignments live.

At the moment, the project includes an assignment library, individual assignment workspaces, practice materials, and progress that can persist in the browser.

The setup is still simple, but separating the marketing site from the Practice Lab helped me understand the project more clearly.

One site explains the idea.

The other is where the work happens.

Behind both sites, I use GitHub to manage the project files and Vercel to publish changes.

Working on them also gave me a repeatable process:

  1. Make one small change.
  2. Test it locally.
  3. Run the production build.
  4. Inspect what Git shows as changed.
  5. Commit the update.
  6. Push it to GitHub.
  7. Check the Vercel deployment.

Those checkpoints make it easier for me to see what happened before moving to the next change.

They have also helped me understand how something I edit locally eventually becomes part of a live website.

Before this project, I understood pieces of that process from the content side.

Now I am working through the sequence myself.

What Broke Along the Way

A lot of the learning came from things that did not work the way I expected.

One of the first confusing areas was the domain setup.

I wanted seovapractice.com to point to the main website and app.seovapractice.com to point to the Practice Lab.

The idea sounded straightforward. Configuring the domains, checking DNS records, and confirming that each one was connected to the correct Vercel project took more effort than I expected.

Navigation between the two sites created another set of small problems.

A button on the main website needed to open the Practice Lab correctly. Links inside the Lab also needed to make sense when someone wanted to return to the main site.

Smaller inconsistencies became easier to notice once both sites were live.

Favicons did not always match.

Branding needed to stay consistent across two separate projects.

Links that worked during local testing still needed another check after deployment.

Git introduced a different kind of confusion.

I started seeing line-ending warnings that looked serious at first. I also had to pay attention to accidental files and changes I did not mean to include in a commit.

I started to see that running Git commands was only one part of the process. I also needed to inspect what Git was telling me before committing anything.

Build and lint output took time to understand too.

At the beginning, a long block of terminal output made it difficult to tell whether I had a real problem or a warning.

I learned to ask more specific questions:

  • Did the build fail?
  • Is this an error or a warning?
  • Which file is causing it?
  • Did my latest change create the problem?
  • Does it need fixing before I push?

I used ChatGPT often during these situations.

Sometimes I needed help interpreting an error message. Other times I needed help figuring out what to check next.

Over time, the process became less about copying a command and more about inspecting the problem, making one change, testing again, and checking whether the result made sense.

One example was Git line-ending warnings. At first, I thought I had broken something. After checking the build and reviewing the changed files, I learned that the warning itself was not the failure I thought it was.

That was a small lesson, but it changed how I reacted to unfamiliar terminal output.

What Building It Is Teaching Me

The biggest lesson so far has less to do with memorizing commands.

I am learning that I do not need to become a professional developer to become more technically capable.

For me, that means understanding enough of the workflow to make a small change, check what happened, test it, and continue without treating every technical step as a black box.

That can be as simple as knowing which file I need to edit, running the project locally, checking whether the production build succeeds, looking at what Git says has changed, and confirming that the deployed version still works.

I still need help with unfamiliar errors and parts of the stack I have not worked with before.

But I am getting better at asking more specific questions.

A warning no longer automatically means something is broken. I can first check whether the build failed.

Before pushing a change, I can inspect the files.

When I need to change several things, I can work through them one at a time and test each step.

That way of working has made the project easier for me to manage.

I can always look up a command when I forget it.

What matters more to me is understanding why I am using it, what I should check afterward, and how it fits into the wider workflow.

SEO VA Practice gives me a reason to repeat that process often enough for parts of it to start feeling familiar.

Why This Matters to Me as a Content Writer

Building SEO VA Practice is changing the way I think about technical content.

I have written about SEO, SaaS products, APIs, data workflows, and technical processes for years. Writing about a process from the outside is different from having to work through it yourself.

A sentence like “connect your custom domain” sounds simple until you are the one checking DNS records and trying to understand why the domain is not pointing where you expect.

The same applies to GitHub.

“Push your changes to GitHub” can look like one small step in a tutorial.

Once you are working with a project, more questions appear:

  • Which files changed?
  • Did I include something by accident?
  • Is this warning harmless?
  • Did the build succeed?
  • Did the deployed version update correctly?

Working through those questions gives me better context for technical writing.

It also makes me think more carefully about documentation.

A useful tutorial should tell someone what to do, but the surrounding details matter too. What should they check first? What should they expect afterward? What should they look at when something does not go as planned?

This experience is also helping me understand web infrastructure more clearly.

GitHub, Vercel, domains, browser storage, APIs, and deployment workflows are becoming less abstract because I am using them in a project I care about.

That matters for SEO and product content too.

When I write about a technical product, I want to understand where a user may get confused, what information they need before starting, and what they should verify after completing a step.

I am still approaching all of this as a content writer and SEO professional.

Building something myself is giving me more context for the products, workflows, and technical systems I write about.

What I’m Building Next

SEO VA Practice is still early.

I want to keep improving the Practice Lab, add more assignments, and learn from the current ones before expanding too quickly.

The first two assignments are already giving me a better idea of what the project needs next.

I want future assignments to stay focused on realistic SEO support work, with clear briefs, useful practice data, and deliverables that require the learner to review information and make decisions.

I also want to keep learning more about the technical side of the project.

That includes how the app is structured, how data should be handled, how progress should be stored, and where APIs or automation may eventually make sense.

I do not want to add technical features just because I can.

Each change should either improve the learning experience or help me understand the workflow better.

This article is the first in a series about the project.

Future articles will document individual parts of the build, including the Practice Lab, my GitHub workflow, Vercel deployment, domain setup, assignment design, and the problems I run into along the way.

Some articles will cover things that worked.

Others will document things I misunderstood, had to fix, or needed help figuring out.

That is the part I want to keep documenting.

SEO VA Practice started as a way to help people practice SEO VA work before getting a real client.

It is also giving me a practical way to become more technically capable while staying grounded in the work I already do in SEO, content, and technical writing.

Follow the SEO VA Practice Build

SEO VA Practice is still an early project. I will continue documenting the assignments, technical decisions, mistakes, and lessons behind the build as it develops.

You can visit SEO VA Practice ↗ or open the Practice Lab ↗.

You can also browse more learning notes, see my professional work, or visit Ed's Lab.