Tecadvance blog articles
Client work
28 B2B articles for a Swiss company blog, each in English and German: 56 pages, written, linked and scheduled to publish in pairs.
- WordPress
- Elementor
- Polylang
- On-page SEO
Web developer & SEO specialist
Information technology coursework alongside hands-on production work on corporate sites, blogs and online stores. I use WordPress and Elementor for content teams, and hand-written HTML and CSS where a page has to be exact. The other half of the job is the technical SEO that decides whether a search engine, or an AI assistant, can read the result at all: structured data, clean slugs, redirects that do not chain.
// What a search engine reads on this page
{
"@type": "Person",
"name": "Evan Prens P. Exanes",
"jobTitle": "Web Developer & SEO Specialist",
"knowsAbout": [
"Technical SEO",
"JSON-LD structured data",
"Generative Engine Optimization",
…
]
}
One piece of client work and four self-initiated WordPress practice builds. Each case study says what the work is, what I did, what you can check and what I would change. The live sites and the source code sit inside the case study they belong to.
Client work
28 B2B articles for a Swiss company blog, each in English and German: 56 pages, written, linked and scheduled to publish in pairs.
Practice project
A four-page company site (Home, About, Services, Contact) built with Elementor's standard widgets on the OceanWP theme, with a Contact Form 7 form.
Practice project
A travel blog with 33 posts, sorted two ways: six categories for the kind of post and a custom Destinations taxonomy for the place.
Practice project
A WooCommerce store with 30 products and 44 variations, and Elementor theme-builder templates for the shop, product, cart and account pages.
Practice project
A one-page personal site from June 2025, with six skill bars and a Hire Me form that opens in a popup, built in Elementor on the OceanWP theme.
Two programs from my first year of BSIT, before WordPress and SEO, both built in two-person teams. They run on a computer, not in a browser, so each has a short case study and the code is on GitHub.
A terminal app for motorcycle maintenance, built in a two-person team. It ranks every open job by how overdue it is, so the most urgent one sits at the top. Passwords are hashed, actions can be undone, and everything saves to a file.
A desktop banking app with dialog-box menus, built in a two-person team. You open an account, deposit, withdraw and transfer, and an account locks after three wrong passwords until an admin unlocks it. Data lives in memory only, which is the first thing I would change.
The one project here about getting found. I used my own portfolio as the test site and measured it, including what the measurements could not show.
Canonical and sharing tags on every page, a sitemap and robots file, and structured data that went from 2 blocks to 4, then checked with Lighthouse on the live pages. Lighthouse scored SEO 100 before and after, so I counted the tags instead.
Short comments from classmates and collaborators on what working with me was like.
A site I finish is a site someone else can run. That means named custom fields instead of hard-coded text, a template for anything that repeats, and a short written handover so the next person is not reverse-engineering my work.
It also means the site is legible to machines. Structured data describes what a page is rather than leaving a crawler to guess from the layout, slugs stay stable so links do not rot, and redirects resolve in one hop instead of a chain. That work is invisible on the page and decides whether the page is quoted at all. That is what AEO and GEO actually mean: being readable to the assistant answering the question, not only to the search index.
Book a 30-minute call. Tell me what the site needs, and I'll tell you honestly whether I'm the right person for it.
Free, 30 minutes on Cal.com. Replies to email within one working day.