Temporary Job Pages and Evergreen Market Resources Chase the Same Query
Evidence: Start with query-to-page data, crawl results, internal links, and the job-feed lifecycle. A problem is visible when the same specialty-and-market search repeatedly switches between short-lived assignment URLs and a durable market resource, when several near-duplicate pages all self-canonicalize without a clear search purpose, or when expired jobs vanish while the market page receives little internal support. Do not label every overlap as cannibalization. Confirm that the pages actually answer substantially similar intent and that search systems are alternating among them.
Consequence: Candidates can reach unstable or outdated entry points, while the agency fragments useful context across URLs that have very different lifecycles. The durable page may never become the consistent place for market guidance, and a temporary job page may be asked to carry information that disappears as soon as an assignment closes.
Correction: Give each page type a clear role. Keep a live assignment page available to search when the opportunity is current and the page is useful. Maintain an evergreen market resource only where the company can provide durable, market-specific information. Connect the two through intentional internal links. Use canonical tags to describe true duplicate or near-duplicate relationships, not to force every assignment into a permanent page regardless of content.
Owner: The SEO lead should define the query and page-role rules with the web or job-feed engineering owner, while recruiting operations owns the status rules that determine when an assignment is open, filled, or retired.
Verification: Re-crawl representative markets, inspect Search Console query and landing-page patterns, follow internal links from market resources to current assignments, and test the chosen closed-job behavior. The source previously used an example in which 50 ER Nurse Phoenix posts competed with the main Phoenix resource while that resource appeared on page 3. Keep it only as an audit illustration, not as a performance forecast.
Severity: critical
Editorial Traffic Does Not Match Assignment Decisions
Evidence: Review high-impression landing pages beside onsite search terms, recruiter call notes, internal content searches, recruiter-assisted actions, and application starts. The mistake is visible when editorial pages attract broad nursing interest but do not answer the practical questions candidates raise about available assignments, licensing logistics, housing considerations, pay terminology, recruiter process, or specialty and market differences. A page can have search demand and still be poorly connected to the decision a travel clinician is trying to make.
Consequence: The company can invest in content that increases visits without improving candidate understanding or helping recruiters connect qualified clinicians with relevant openings. Broad informational traffic is not automatically harmful, but it should not be mistaken for evidence that the editorial program supports assignment discovery.
Correction: Build the content map from real candidate questions and the decisions that occur before an application or recruiter conversation. Separate informational education from assignment-selection support, connect useful resources to relevant current jobs, and have the appropriate reviewers assess statements involving licensing, tax, compensation, credentialing, employment, or healthcare. Avoid writing clinical advice simply to expand a specialty page.
Owner: The content lead owns the editorial map, recruiting subject-matter staff supply recurring candidate questions and operational context, and the responsible reviewer owns approval of regulated or employment-adjacent claims.
Verification: Compare the queries a page earns with the actions and questions that follow. Review whether readers continue to a relevant assignment, recruiter resource, or application step and whether recruiters report fewer unresolved content gaps. The source's contrast between 'travel nurse salary' and 'travel nurse housing stipend San Francisco' is best treated as an intent example, not proof that either phrase has a universal conversion advantage.
Severity: high
JobPosting Markup Drifts From the Live Assignment
Evidence: Compare the visible job detail, the job-feed record, rendered structured data, and the current page state. Look for missing JobPosting markup on a valid live role, required properties that are absent, machine-readable values that disagree with what a candidate can see, or markup that still describes an opportunity after the assignment has closed. Validation tools help identify syntax and property issues, but they do not replace checking whether the underlying job is genuinely current.
Consequence: A page can become ineligible for Google's job search features or send inconsistent information about the assignment. The source previously stated that the job feature captured 40-60% of job-related clicks. No supporting source URL for that figure appears in this JSON, so it remains a historical claim requiring source reconciliation rather than a current benchmark.
Correction: Generate JobPosting JSON-LD from the same source of truth used to render the assignment, and keep the title, location, employment details, dates, and status aligned with visible content. When a role closes, apply the site's documented retirement policy and update or remove structured data accordingly. Do not use markup to describe details that are unavailable or contradicted on the candidate-facing page.
Owner: Web or job-feed engineering owns generation and deployment, recruiting operations owns assignment-state accuracy, and the SEO owner checks that the implementation remains valid and consistent with the rendered page.
Verification: Test a sample of live and closed roles in structured-data validation, inspect the rendered source, compare each result with the feed record, and walk from the search landing page to the application. The prior source placed a Boston ICU role on page 5 in an example where markup was missing. Treat that as an illustrative scenario only, not evidence that adding markup produces a ranking change.
Severity: critical
Fast Enough Does Not Mean Easy to Apply on Mobile
Evidence: Put field performance beside application analytics and manual device testing. Warning signs include slow or unstable job templates, controls that move while loading, form fields that are difficult to read or tap, resume upload that fails or is awkward on a phone, consent controls that are hard to operate, and abandonment concentrated around mobile-specific steps. The source used more than 3 seconds as an example threshold. Treat the actual field and funnel data for the site's users as the decision evidence instead of turning that example into an official cutoff.
Consequence: A clinician can leave before the recruiting team receives a complete application or usable contact action even when the page eventually renders. The source also cited a 20-40% conversion-rate drop without a supporting source URL in this JSON. Preserve it as a historical claim that requires source reconciliation, not as a promised effect size for this site.
Correction: Remove unnecessary script and image weight, reserve layout space, simplify the mobile form, make upload and consent steps operable on common phones, preserve entered values when validation fails, and prioritize templates that receive organic job traffic. Performance work should include the search result landing page, job detail, and application steps rather than stopping at the homepage.
Owner: Front-end engineering owns template performance and interaction defects, product or recruitment operations owns the application flow, and analytics support owns reliable step-level instrumentation.
Verification: Review Core Web Vitals field data where available, test representative real devices and slower connections, complete the entire application manually, and compare step abandonment before and after the correction. A technically acceptable speed score does not verify that resume upload, consent, validation, and submission are usable.
Severity: high
Backlink Targets Reward Count Instead of Editorial Fit
Evidence: Inspect new referring pages one by one rather than reading a total link count. A quality problem is visible when placements come from unrelated sites, templated pages, or low-context directories that have little connection to nursing careers, healthcare workforce topics, staffing, or the resource being cited. Also check whether the surrounding sentence actually needs the destination page as support; a relevant domain does not make an irrelevant citation useful.
Consequence: Budget and outreach effort can be consumed by references that add little reader value or qualified discovery, while manipulative placement patterns can create avoidable search-quality risk. E-E-A-T is useful as a way to think about experience, expertise, authority, and trust signals in content and reputation, but it should not be converted into a numeric backlink score.
Correction: Create assets that deserve citation, contribute recruiter or workforce expertise where it is genuinely relevant, pursue editorial digital PR and partnerships with clear audience fit, and reject placements whose only purpose is link volume. The earlier source contrasted 100 generic links with a single relevant reference and mentioned Nurse.org or a state nursing board. Preserve that contrast only as an example of why context matters, not as a formula for ranking weight or endorsement value.
Owner: Digital PR or partnerships owns prospecting and placement quality, the SEO lead reviews search risk and destination relevance, and a subject-matter reviewer checks healthcare or workforce assertions used to earn coverage.
Verification: Sample acquired links for topical fit, editorial independence, surrounding context, destination usefulness, and referral behavior. Record why the reference makes sense for a reader and separate qualified referral activity from raw referring-domain growth when assessing the program.
Severity: medium
Local Pages and Profiles Overstate or Conflict With Real Offices
Evidence: Compare the website, Google Business Profile, major citations, and internal operations records for each real recruitment office. The mistake is visible when names, addresses, phone details, hours, or office status conflict; when an obsolete address continues to appear; or when a service market is presented as though the company maintains a staffed physical location there. Also flag local landing pages whose copy is interchangeable and provides no genuine local contact or recruiting context.
Consequence: Candidates can receive conflicting information about where a recruiting team can be contacted and whether an office is real, and search systems can receive inconsistent entity data. This is primarily an accuracy and user-trust problem; profile completeness or activity should not be presented as a guaranteed ranking mechanism.
Correction: Maintain accurate profile and citation data only for eligible real-world locations, remove obsolete office information, and publish a dedicated location page only when there is a genuine office or location that supports useful location-specific information. Serving assignments in a market does not by itself justify manufacturing a local office page.
Owner: The local SEO owner coordinates the public records, while operations or facilities staff confirm address, phone routing, office status, and other facts before changes are published.
Verification: Match each real office across internal records, the website, Google Business Profile, and the major citations the team actively maintains. Then inspect the location page to ensure its information is locally useful and accurate. The prior Denver example is most useful as a consistency scenario: an obsolete address can misdirect a candidate even when recruiters continue serving assignments in that region.
Severity: medium
Specialty Pages Stop at the Job Feed
Evidence: Read the specialty page as a clinician would when current openings change. A thin page typically has a generic introduction, a feed, repeated copy shared with other disciplines, and little explanation of how the agency supports a specialty search. A page focused on L&D Travel Nurse Jobs should provide more decision context than a title followed by vacancies, while still avoiding invented clinical instruction.
Consequence: The page loses most of its usefulness when individual assignments close and gives candidates little reason to return to the durable specialty resource. It can also become difficult for recruiters and search systems to distinguish the page from other feed-only collections that contain the same openings.
Correction: Add accurate, reviewed information about how recruiters handle matching, what assignment facts the agency publishes, how credentialing and licensing resources are surfaced, what specialty-specific candidate questions recur, which market considerations are relevant, and how the current job feed connects to those decisions. The source previously used 800 words as an editorial target. Treat that as a planning example only, not as a Google requirement or a minimum for usefulness.
Owner: The content lead owns page completeness, recruiter subject-matter staff supply operational context, and responsible reviewers assess healthcare, licensing, credentialing, compensation, or employment statements before publication.
Verification: Confirm that the page remains useful without relying solely on the current feed, links accurately to available assignments, answers documented candidate questions, and earns queries consistent with the intended specialty. The earlier Psych example described a page with only 3 jobs and no meaningful specialty context. Keep that as an audit illustration, not as a minimum-content rule.
Severity: high
