You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Telnyx

Technical AEO/SEO Specialist

  • Office
  • 3-6 years

Salary

Not stated

Similar roles pay $85K - 160K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds a private, global, multi-cloud IP network and delivers edge connectivity through APIs, aiming to link people, devices and applications.

It is financially stable and profitable, and it invests in new technologies and in continuous learning for its team.

The work sits on the AEO team, which looks after the quality, accuracy and AI-readiness of the public website.

Responsibilities

  • Act as the final quality check for the website, reviewing every new and changed page before and after it goes live. Cover titles, meta tags, H1s, canonicals, schema, internal links, images, forms and mobile layout.
  • Check work from Product Marketing, DevRel and Dotcom, which publish constantly, so no page goes live broken, wrong or hidden from search engines and AI agents.
  • Make sure every claim about features, regions, models, numbers and compliance is true and current. Correct any page that overstates, omits or misleads.
  • Fix problems yourself by opening a pull request when you can. When you cannot, write a Linear ticket with the evidence and the exact fix needed.
  • Run AI agents through key tasks such as checking a price, signing up and making a first API call daily, and fix whatever breaks.
  • Keep each page's markdown twin matching its HTML word for word. Confirm that requests sent with Accept: text/markdown return clean markdown and that each page links to its twin.
  • Run the Ora.ai scan on every release and on a daily check, and keep the site at an A+ agent-readiness score by fixing what it flags.
  • Make sure AI agents can read key answers on the homepage, pricing and docs in the raw HTML, since agents that only fetch pages cannot run JavaScript.
  • Test firewall and bot rules against major AI crawlers, including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and crawlers that fetch on a user's behalf. Check server logs so a single 403 does not block them all.
  • Keep llms.txt valid under the v2 spec for the root and each section of the site and docs, with every link working and every file matching what is live.
  • Keep llms.txt, the API catalog, the OpenAPI spec, the agent skills index and the MCP server card live, valid and linked from page headers and the footer.
  • Maintain robots.txt and its content signals so they correctly state which AI crawlers may search, fetch or train on the content. The file must never error or return HTML.
  • Crawl the main site and satellite sites in Screaming Frog every day to find broken links, redirect chains, orphan pages, metadata problems, canonical errors and indexing issues.
  • Own the launch checklist for new sections, redesigns and URL changes. Confirm sitemaps, indexing, twins and llms.txt on launch day, then watch for regressions over the following weeks.
  • Build automated checks that run after each deploy, comparing pages with their twins, the pricing source and the discovery files, and alert when they stop matching.
  • Review emerging agent standards each quarter, such as NLWeb, A2A, Web Bot Auth and agent payment protocols, and recommend which ones to adopt.

Requirements

  • Have 2 to 3+ years in technical SEO, web QA or web development, or equivalent hands-on work you can show.
  • Care deeply about accuracy and check the source before approving any page, especially prices and feature claims.
  • Be a daily Screaming Frog user who sets up custom extractions and segments and turns crawl exports into prioritized fix lists quickly.
  • Be comfortable in Git and GitHub and able to open clean pull requests for metadata, schema, links or copy fixes, and know when to pass work to Engineering.
  • Read HTML, CSS and JavaScript well enough to debug rendering, canonicals, redirects, status codes and headers.
  • Understand how AI agents read the web, including llms.txt, markdown twins, Accept: text/markdown, AI crawler user agents, robots.txt policy, and why JavaScript-only content and 403 responses block agents.
  • Know crawling, indexing, sitemaps, structured data and Core Web Vitals, and which of these matter for Google and which matter for AI agents.
  • Work at speed on a steady flow of pages from fast-moving teams without missing small issues or becoming a bottleneck.
  • Have used scripts, APIs or AI agents such as Python, JavaScript, Claude Code or Cursor to automate audits, comparisons or alerts.
  • Be comfortable in Google Search Console, GA4 and Ahrefs or Semrush, and able to show whether a fix changed results.
  • Communicate clearly and calmly, able to tell a PMM about a pricing error in one Slack message with the evidence and fix, while staying friendly.
  • Track every issue in Linear with a ticket, an owner and a status so anyone can see progress without asking.
  • Bonus: experience with Next.js, React or Vercel, including server-side rendering, static generation and JavaScript SEO.
  • Bonus: experience shipping llms.txt, markdown twins or agent discovery files on a live site, or raising an agent-readiness score with Ora.ai, is-agentic or Lighthouse's agentic browsing audit.
  • Bonus: experience with a headless CMS such as Contentful or Sanity, including content models and publishing workflows.
  • Bonus: comfort with CDN and firewall settings such as caching, bot rules and headers on Cloudflare or Vercel, enough to spot crawler blocks.
  • Bonus: server log analysis to see which search and AI crawlers visit which pages and what they receive.
  • Bonus: automated testing with Playwright or Cypress that catches SEO or content regressions in CI.
  • Bonus: Python or SQL for pulling data, comparing crawls or checking pages at scale.
  • Bonus: familiarity with OpenAPI specs, API docs or MCP servers, so you can QA developer pages and the files agents use.
  • Bonus: experience at a developer tool, API, cloud or telecom company, where pages must be technically accurate.
  • Bonus: site migration experience, including URL mapping, launch-day checks and post-launch cleanup.
  • Bonus: international SEO, including hreflang and localized pages.
  • Bonus: accessibility basics such as accessible names, form labels and document structure, which help screen readers and browser agents.

Where you’d work

From the office

About the company

Telnyx

Office in United States

Also hiring in Warsaw, Poland, Dublin, Ireland, London, United Kingdom and 1 more place

6 of their 12 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation
Tech stack
  • SQL
  • SEO
Specialty
Performance
Region
United States
Pay period
Annual
Show 5 more factsShow less

Role

Category
Marketing
Specialty
Performance
Experience
3+ years
Tech stack
  • SQL
  • SEO

Location

Work model
Office
Region
United States
Office
  • United States

Compensation

Salary
Salary by agreement
Pay period
Annual

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason