DEV Community: Autumn Morgan

End-to-End SEO Testing with Playwright and Lighthouse

Autumn Morgan — Thu, 06 Mar 2025 15:39:13 +0000

Automated testing is second nature for developers—it ensures our applications remain reliable, secure, and consistent as they evolve. But what about SEO? Search engine optimization is crucial to a website’s visibility, directly impacting traffic, conversions, and overall success. While SEO audits have traditionally been a manual process, automation is changing the game.

With the right tools, we can use end-to-end (E2E) testing to audit key SEO factors, ensuring our web applications follow best practices without constant manual checks. In this article, we’ll explore how to use Playwright, Puppeteer, and Vitest to integrate SEO auditing into your test suite, making search engine optimization a seamless part of your development workflow.

What is SEO?

SEO, short for search engine optimization, is the practice of improving your website’s visibility in search engines. It helps search engines understand your content and ensures users can find your site, decide whether to visit and have a smooth experience once they do.

Headless Browsers

Headless browsers—browsers without a graphical user interface—are widely used in automation. Many, like Chrome’s headless mode, include built-in tools to assess SEO, accessibility, and performance. One of the most well-known tools for this is Lighthouse, which provides automated reports on SEO issues and web performance metrics.

Choosing a Test Framework for SEO Audits

In the software development world, we have a lot of test framework tools. In this article, we will discuss 2 of them: Vitest and Microsoft Playwright

Vitest

Vitest is a next-generation JavaScript testing framework powered by Vite. It’s an excellent alternative to Jest, offering native TypeScript support, a fast setup, and solid performance. However, while it has an experimental headless browser, it’s not ideal for advanced scenarios like running SEO audits in CI/CD pipelines. Instead, we can pair Vitest with Pupetter, a more mature tool for headless browser automation.

Playwright

Playwright is a robust framework built specifically for end-to-end testing. Unlike Vitest, It was designed to handle real browser interactions, making it ideal for SEO audits. It supports Chromium, WebKit, and Firefox, runs on Windows, macOS, and Linux, and can execute tests in both headless and headless modes. Playwright even includes native mobile emulation to test how pages render on mobile devices.

Lighthouse: The SEO Testing Powerhouse

Lighthouse is an open-source, automated tool for improving the quality of web pages. It can be run on any public or authentication-requiring web page. It offers audits for performance, accessibility, progressive web apps, SEO, and more.

Practical Example: Running an SEO Audit with Playwright

To put theory into practice, we’ll learn how to configure Playwright to perform automated SEO audits on a website. By the end, you'll see how easy it is to integrate SEO testing into your development workflow—catching issues before they impact your search rankings.

Requirements:

The Playwright config file

Playwright provides extensive options for customizing test execution. The configuration file allows us to set up test parallelization, specify the test directory, define a base URL for the page, use the page.goto(...) method, and configure multiple projects.

Playwright provides extensive configuration, allowing developers to customize test execution. The configuration file lets us:

✅ Set up test parallelization.

✅ Specify the test directory.

✅ Define a base URL for `page.goto(...).

✅ Configure multiple projects.

In the projects section, we can define which browsers to use, such as Chromium, Firefox, and Safari, and device-specific settings. This ensures that tests run with the correct configurations, whether we're testing desktop or mobile experiences.

📌 Example: Playwright Config File Setup

Writing SEO-Focused Tests with Playwright

Getting Started with Playwright

Creating tests in Playwright is straightforward—it’s similar to Jest. Simply create a .ts file in the tests folder, import test, and expect from @playwright/test. Playwright provides a page object that allows interaction with a webpage just like a real user.

📌 Example: Using the Page Object in Playwright

One of Playwright’s most powerful features is locators, which help us find elements, interact with them (click, type, etc.), and make assertions.

Common locator methods include:

page.getByRole(): Find elements by accessibility attributes
page.getByText(): Locate elements by text content
page.getByLabel(): Identify form inputs based on associated labels
page.getByPlaceholder(): Locate inputs using placeholder text
page.getByAltText(): Find images by alternative text
page.getByTestId(): Locate elements using a custom test attribute

Need finer control over which browser or rendering engine to use for specific tests? Playwright makes it easy. Simply import the required configurations from @playwright/test.

More details here.

📌 Example: Running Tests on Specific Browsers

Writing SEO Tests in Playwright

Configuring a Base URL

To streamline navigation, we can define a Base URL in playwright.config.ts. This allows us to use relative paths instead of specifying complete URLs in every test.

📌 Example: Setting a Base URL in playwright.config.ts

SEO-Specific Tests

Let’s look at some essential SEO checks that can be automated with Playwright.

1️⃣ Page should have a favicon.

2️⃣ Robots.txt should be valid.

3️⃣ Sitemap should be valid.

Note: Some web servers might return a compressed gz file with `XML' (as the Planet Argon Website does), so we test both possibilities.

4️⃣ Page should have a valid meta description.

5️⃣ Page should have a valid title.

6️⃣ Page should have a valid viewport meta tag.

7️⃣ HTML tag should include a lang attribute.

Running Lighthouse Tests with Playwright

To integrate Lighthouse audits with Playwright, install playright-lighthouse.

Threshold tests

Lighthouse allows us to define thresholds for key performance categories:

✅ Performance

✅ Accessibility

✅ SEO

✅ PWA

✅ Best Practices

If we pass nothing in the config, all categories will be tested and all scores will be 100 (default value).

Before writing Lighthouse tests, we must adjust some configurations in the playwright.config.ts file and create a new Lighthouse-specific project.

This is necessary to ensure that Lighthouse tests run with a single worker (by setting the worker count to 1), which helps avoid potential concurrency issues. Additionally, we need to configure Playwright’s Chromium browser to launch with port 9222 open, allowing Lighthouse to communicate with it during audits.

Lighthouse Test: Accessibility & Performance

Accessibility score should be above 90 and Performance above 70.

Very good! All your tests passed!!

Final Thoughts

By incorporating end-to-end SEO testing with Playwright and Lighthouse, you can proactively catch SEO issues before they affect your rankings. Automating these tests in your CI/CD pipeline ensures that SEO remains a continuous, seamless part of development while helping to improve your site’s search engine rankings and overall performance.

References

1 - SEO Starter Guide

2 - Lighthouse Overview

3 - Vitest Guide

4 - Playwright Intro

5 - Abhinaba Ghosh/Playwright/Lighthouse

This article was written by Evaldo Klock and originally published on Planet Argon's blog.

How to Manage an End-of-Day Client Emergency

Autumn Morgan — Tue, 25 Feb 2025 21:22:15 +0000

We've all been there: You're packing up for the day, ready to disconnect, when suddenly—ping! An urgent Slack message from a client. Your heart races, your to-do list is out the window, the client is in crisis mode, and the pressure is on.

It's easy to feel overwhelmed in these moments, but the key is staying composed and handling the situation systematically.

Let's break down how on of our developers, Liz Pantalone, navigated an end-of-day client emergency and what we can learn from her approach.

Respond Quickly and Acknowledge the Issue

When an emergency hits, the first instinct might be to jump straight into troubleshooting. But before you do anything else, pause and respond. Acknowledge the client's message promptly. Even if you don’t have an immediate solution, letting them know you’re aware of the issue reassures them that help is on the way.

"I’ll take a look.”

Why It Matters:

Clients in crisis need to feel heard. A quick acknowledgment reassures them that their issue is a priority.
Even if you can't solve the problem immediately, a fast response shows you're on it.

Gather the Details

Before diving into the issue, you need a clear understanding of what’s going wrong. Assumptions can lead you down the wrong path. Ask specific, clarifying questions to gather all relevant details. Focus on understanding the scope and specifics of the problem.

"Could you let me know which file you were attempting to overwrite? If you could share the link to it…”

Why It Matters:

Asking the right questions saves time in the long run.
It shows the client you're methodical and invested in solving their problem.

Validate and Narrow Down the Problem

Once you have the details, the next step is to verify the issue. Is it isolated, or part of a larger problem? Try to reproduce the issue in a controlled environment. Test similar scenarios to identify whether the problem is specific or systemic.

"I was able to successfully replace a test PDF file with a PEG file. So let’s see what may be different about the C&C file.”

Why It Matters:

This helps isolate the root cause by eliminating variables.
It builds client confidence as they see you're approaching the issue systematically.

Investigate Thoroughly

Now it’s time to dig deeper. Surface-level checks might miss hidden issues. Review system logs, database records, and other diagnostic tools to uncover anomalies or errors. Look beyond the obvious.

"Ok, I will look at the logs to see if I see anything in the last few minutes.”

Why It Matters:

Logs often reveal hidden issues that aren't immediately visible.
Proactive investigation helps uncover if the problem lies with user input, system configuration, or external factors.

Encourage Collaboration

Troubleshooting doesn’t have to be a solo mission. Engaging the client can lead to faster results, so keep them in the loop. Ask them to perform specific actions while you monitor the system, turning troubleshooting into a collaborative effort.

"It could be. Want to try again while I check the logs?”

Why It Matters:

Collaborative troubleshooting speeds up resolution.
It keeps the client informed and makes them feel like part of the solution.

Document Lessons Learned

Once the issue is resolved, don’t just move on. Take a moment to reflect. Document what went wrong, how it was resolved, and any gaps in the system that contributed to the problem. Suggest improvements if needed.

"Could we have a ticket for Extranet File Upload Module to add more user-facing error handling?”

Why It Matters:

Post-mortem analysis helps improve systems and prevent future issues.
Documenting lessons learned ensures continuous improvement.

Maintain Professionalism and Empathy

Crises are stressful—for both you and the client. Your demeanor matters. Stay calm, professional, and empathetic. Reassure the client that you’re in control, even if you’re still troubleshooting behind the scenes.

"Well, I’m happy it’s working!”

Why It Matters:

Empathy builds trust. Clients often feel stressed in these situations.
A calm, understanding approach can make a big difference in the client’s experience.

Follow Up and Close the Loop

Resolution isn’t the end of the story. Clear follow-up ensures nothing falls through the cracks. Once the issue is resolved, confirm with the client that everything is working as expected. Let them know how to reach you if any further issues arise.

"I’m going to head out for now. But I’ll have Slack on my phone if anything else pops up.”

Why It Matters:

Clear communication ensures the client feels supported even after the issue is resolved.
It provides closure and reassurance that you're still available if needed.

Proactively Suggest Improvements

Don’t just fix the problem—help prevent it from happening again. Identify opportunities for system improvements and suggest them to the client or your team. Proactive recommendations demonstrate your commitment to quality.

"The system needs to have some more error handling added in there to help the user out if this happens again.”

Why It Matters:

Proposing improvements shows you're thinking ahead and committed to excellence.
Clients appreciate developers who proactively suggest ways to enhance their systems.

Key Takeaways for Handling Client Emergencies

When faced with a last-minute emergency, keep this checklist in mind:

Acknowledge the issue immediately to reassure the client.
Ask clarifying questions to fully understand the problem.
Reproduce the issue and narrow down potential causes.
Investigate logs or system details for deeper insights.
Keep the client informed and collaborate as needed.
Document lessons learned to prevent similar issues.
Remain calm and empathetic to build trust.
Ensure clear follow-up to close the loop.
Propose proactive improvements to enhance the system.

By following these steps, you can turn an end-of-day emergency into an opportunity to showcase your problem-solving skills and professionalism. Liz's approach is a great example of how to handle urgent client issues with care, competence, and a collaborative mindset.

The next time you find yourself in a similar situation, take a page from her playbook!

The Truth About LinkedIn Newsletters in 2025

Autumn Morgan — Tue, 11 Feb 2025 16:02:04 +0000

Last year, we wrote about what to expect when starting a LinkedIn newsletter in 2024, just as Planet Argon launched a newsletter for Maintainable Podcast. A lot has changed since then. Some things worked better than expected, some fell flat, and LinkedIn has rolled out a few updates along the way.

So, if you’re thinking about launching a LinkedIn newsletter in 2025 — or wondering if it’s still worth it — here’s what you need to know.

Are LinkedIn Newsletters Still Worth It in 2025?

Short answer: It depends on what you want out of it.

If your goal is to build brand visibility, spark conversations, and grow your presence on LinkedIn, then yes — it’s still a solid tool. LinkedIn continues to push newsletters into people’s feeds, and if your audience is active on the platform, you can build up a subscriber list faster than you would with a regular email newsletter.

But if you’re hoping to own your audience, collect emails, and have full control over how you reach people, LinkedIn still isn’t the best option. Your subscribers belong to LinkedIn, not you. And if LinkedIn ever changes its algorithm (which it probably will), your reach could take a hit overnight.

If you’re okay with playing by LinkedIn’s rules, a newsletter can be a great way to get in front of more people. But if you want more control, pairing it with your own email list is a smarter long-term play.

What’s New for LinkedIn Newsletters in 2025?

LinkedIn has made some tweaks, but the core experience is still the same. Here are a few key updates:

Better discovery tools — LinkedIn now shows newsletters in search results more often, making it easier for new people to find yours.

More customization options — You can now tweak the layout and branding a little more to match your style.

Auto-follow is stronger — When someone subscribes to your newsletter, they automatically follow your LinkedIn page (which helps with visibility).

Still no email access — If you were hoping LinkedIn would finally let you export your subscribers’ emails… nope.

What We Learned from Running a LinkedIn Newsletter for a Year
At Planet Argon, we launched a LinkedIn newsletter last year to see if it could help grow the audience for our podcast, Maintainable.fm. Here’s what we found:

What Worked

✔️ We gained new listeners — Some subscribers did check out the podcast, which was a win.
✔️ It was easy to grow — LinkedIn automatically invites your connections to subscribe, so we got a decent number of followers fast.
✔️ Posts got more engagement — Newsletter posts tended to get more likes and comments than regular LinkedIn posts.

What Didn’t Work

❌ No email control — We couldn’t follow up with subscribers outside of LinkedIn.
❌ Limited analytics — The insights weren’t detailed enough to tell us how many readers actually became listeners.
❌ Time investment — Writing, designing, and posting took effort, and the return wasn’t huge.

Strategies for Maximizing Engagement

If you’re going to start (or keep running) a LinkedIn newsletter in 2025, engagement is key. Otherwise, it’s just another post lost in the feed. Here are a few ways to keep people reading, commenting, and coming back for more:

Write for skimmers, not just readers

Most people won’t read every word of your newsletter — so make it scannable. Use:
✔ Bullet points (like this!)
✔ Short paragraphs
✔ Bold text for key takeaways

Keep it real (and avoid sounding robotic)

People scroll past generic, corporate-sounding content. The more human and conversational you sound, the better. Share stories, insights, or even lessons from failures. Readers connect with real experiences, not just polished “expert advice.”

Leverage LinkedIn’s auto-follow feature

When someone subscribes to your newsletter, they now automatically follow your page — so make sure your LinkedIn page is active and engaging. More followers = more reach.

Cross-promote everywhere

Don’t let LinkedIn’s algorithm decide your reach. Share your newsletter:

On your website (e.g., “Read our latest issue on LinkedIn”)
In your email signature
In other social media posts
In relevant LinkedIn groups (if it makes sense for the audience)

End with a strong CTA

Every newsletter should guide your audience to do something next:

Comment with their thoughts
Visit your website or listen to your podcast
Share with their network
Click a link to learn more

Make it easy and clear — otherwise, people will just scroll on by.

Should You Start a LinkedIn Newsletter in 2025?

If you’re considering it, ask yourself:

Is my audience already active on LinkedIn? If yes, a newsletter could be a great way to reach them.
Do I want control over my email list? If yes, then LinkedIn alone isn’t enough — you’ll need another email platform.
Do I have the time to create consistent, high-quality content? If no, a LinkedIn newsletter might just become another thing on your to-do list that doesn’t get the results you want.

How to Make a LinkedIn Newsletter Work for You

If you do decide to go for it, here’s what will help:

✅ Keep it short and valuable — Nobody wants a 1,500-word newsletter in their LinkedIn feed. Get to the point.
✅ Use strong visuals — Posts with images or graphics tend to perform better.
✅ Have a clear CTA — Tell readers what you want them to do next (visit your website, listen to your podcast, download something, etc.).
✅ Promote it elsewhere — Don’t just rely on LinkedIn’s algorithm. Share your newsletter on other social channels and your website.

Final Thoughts: Is It Worth It?

For us, the LinkedIn newsletter is not a game-changer. It helped grow our visibility on LinkedIn, but it didn’t replace the need for our own email list or other marketing efforts.

LinkedIn newsletters can still be a great tool in 2025, but they’re not a magic bullet. The key is using them strategically — as part of a larger marketing plan, not the whole thing.

Are you running a LinkedIn newsletter? What’s working (or not working) for you? Let’s compare notes in the comments.

Re-tooling the Retro Way: Ditching Hubspot for Leaner, Simpler Marketing

Autumn Morgan — Wed, 29 Jan 2025 19:29:17 +0000

In a world where efficiency reigns supreme, developers and marketers are ditching bloated, one-size-fits-all platforms in favor of streamlined, customizable tools. Our marketing team recently took the plunge and said goodbye to HubSpot, opting for a leaner, more modular tech stack. Here's how—and why—we did it.

The Shift to Simpler Tech Stacks

We aren't the only ones! Marketers prefer a more personal and authentic approach to their strategies, and some bigger platforms tend to feel more robotic in their structure. Inspired by the rise of microservices in software development, this simpler approach values focused, specialized apps over monolithic platforms.

Why the Shift?

More Control: We tailor tools to fit our processes instead of conforming to rigid systems.
Customizability: Lightweight tools are easier to tweak and optimize.
Lower Costs: Stop paying for bloated platforms we don’t fully utilize.
Integration Freedom: Modular tools integrate seamlessly with our ecosystem.

Examples of This Shift

Companies are breaking away from heavyweight tools and opting for leaner, modular tools that do just enough without the extra bloat. Here are some options we looked into and discussed with other marketing coordinators. Not all of these tools are created equally, so it’s important to know what your goals are and what solutions you’re looking for. A few of these tools allow you to embed code, customize options, and integrate with other tools, so this part takes a little time and research.

CRM Alternatives

Pipedrive: Ideal for smaller teams needing a visual, pipeline-focused CRM.
Zoho CRM: A customizable, affordable CRM with modular add-ons for scaling.
Copper: Built specifically for teams already using Google Workspace.

Email Marketing Alternatives

Kit (formerly ConvertKit): Minimalistic yet powerful, perfect for newsletters and audience segmentation.
Buttondown: A lightweight option for managing email campaigns and subscriber lists.
Mailchimp: Classic tool for ease and automation

Forms and Surveys

Typeform: Clean, interactive, and user-friendly for creating engaging forms and surveys.
Jotform: Customizable forms for various use cases, from lead capture to payment collection.
Google Forms: Free and accessible, with easy data collection and export.

Automation Alternatives

Zapier: The Swiss Army knife of automation, connecting virtually any app.
Make (formerly Integromat): Affordable and great for more complex workflows.
n8n: An open-source workflow automation tool for teams that want flexibility and control.

Marketing Analytics Alternatives

Google Analytics 4: Comprehensive and free for tracking web traffic and user behavior.
Hotjar: Focused on user experience with heatmaps, session recordings, and feedback forms.
Mixpanel: Advanced analytics for tracking product usage and customer journeys.

Why We Ditched HubSpot

When it comes to marketing tools, bigger doesn’t always mean better. For years, HubSpot has been our all-in-one platform, offering everything from email campaigns to analytics to forms. But over time, we realized we were paying a premium for features we barely used, while the tools we did need felt bloated and inflexible. It wasn’t just a question of cost—it was about freedom, customization, and staying agile in an ever-changing marketing landscape. This motivated us to find tools that empower us to work smarter, not harder while aligning better with our team’s unique workflows and values.

What Are the Right Tools for the Job?

The key to a streamlined, effective marketing stack isn’t having more tools—it’s having the right tools. After stepping away from an all-in-one platform, we reimagined our approach with a modular toolkit designed to do exactly what we need—no more, no less. By focusing on purpose-built apps for specific tasks, like Zapier for automation or Kit for email marketing, we’ve created a flexible, efficient system that’s easy to manage, integrates seamlessly, and leaves room for creativity and growth. Here are the primary tools we’ve chosen to work with.

Zapier: Capturing leads with ease using forms embedded on service and contact pages.
Kit: A simple, reliable email tool for newsletters and forms.
Custom Tools & Google Forms: For workflows that don’t fit into cookie-cutter solutions.

What About Workflows That Don’t Fit?

Not every workflow can be neatly packaged into a shiny new tool—and that’s okay. Some of our workflows required custom solutions or simpler, more traditional approaches. For example, we’ve embraced tools like Google Forms for quick surveys or feedback collection and rely on downloadable PDFs for resources like toolkits and guides.

Building a Leaner, Smarter Future

By embracing a lean, modular approach, we’ve unlocked the freedom to innovate, collaborate, and focus on what truly matters: building meaningful connections, driving creativity, and aligning our tools with our values. Whether you’re a marketer looking for flexibility or a developer striving for efficiency, this shift empowers teams to think bigger with smaller, smarter tools. It’s not just a tech stack—it’s a strategy for a brighter, more agile future.

Troubleshooting Docker Desktop: Tips and Alternatives for Developers

Autumn Morgan — Tue, 21 Jan 2025 18:47:56 +0000

Docker Desktop is a go-to tool for many developers, but it’s not without its challenges. From managing specific versions to finding alternatives with a lighter footprint, our team recently shared tips and solutions that might help you streamline your container workflows. Here’s what they had to say, along with some actionable advice.

Downloading Specific Versions of Docker Desktop

If you need a specific version of Docker Desktop—especially for compatibility reasons—William Mena shared a practical approach, referencing this Docker Community Forums thread:

1. Locate the Build Path: Find (ctrl/cmd + f) the version you want in the Docker Desktop Release Notes. For instance, version 4.26.1 corresponds to build path 131620.

2. Modify the Download Link: Update the appropriate link below, replacing BUILD_PATH_NUMBER with your specific build path number:

Apple Silicon: https://desktop.docker.com/mac/main/arm64/BUILD_PATH_NUMBER/Docker.dmg
Apple Intel: https://desktop.docker.com/mac/main/amd64/BUILD_PATH_NUMBER/Docker.dmg
Windows ARM64: https://desktop.docker.com/win/main/arm64/BUILD_PATH_NUMBER/Docker.dmg
Windows AMD64: https://desktop.docker.com/win/main/amd64/BUILD_PATH_NUMBER/Docker.dmg

The Docker forums also mention you can replace Docker.dmg with Docker Desktop Installer.exe.

This method allows you to re-install specific versions to resolve compatibility issues.

Exploring Alternatives to Docker Desktop

Docker Desktop’s limitations—like performance issues and subscription requirements—can be frustrating. Here are some alternatives discussed:

Podman: A lightweight container runtime that eliminates the need for a desktop app. It’s free, open-source, and compatible with many Docker workflows.
OrbStack: Although it’s a paid tool, OrbStack promises faster, lighter, and simpler container and Linux management compared to Docker Desktop.
Colima: This tool offers container runtimes on macOS and Linux with minimal setup. It’s free and negates the need for a desktop app altogether. Robby noted that this might be the simplest solution for some setups.

Troubleshooting Common Docker Issues

William also shared a recurring issue:

"Once every few months, I’m unable to edit the front-end React code due to a JSON parsing error. Clearing the cache or using Docker Desktop’s purging tool doesn’t fix the issue. I have to uninstall Docker and reinstall a specific version to resolve the problem."

If you’ve faced similar issues, here are some tips:

Monitor Disk Usage: Check if container storage is nearing capacity.
Clear Unused Containers: Use docker system prune to remove unused containers, networks, and images.
Backup and Reinstall: When all else fails, a clean re-install of a reliable Docker version might save time in the long run. William clears Docker-related files using an application called AppCleaner.

Additional Resources

Container Configuration Help: Use this Docker troubleshooting guide for managing container issues.
Stay Open to Alternatives: Explore tools like Podman and Colima to save headaches and provide better performance in the long run.