No. The math runs in your existing due-date widget, which handles the LMP-versus-conception-date convention, the 280-day Naegele calculation, and the trimester-boundary logic. SleekRank reads the week-row from your sheet and renders the surrounding milestone, symptom, screening, and FAQ copy. The widget consumes the week_number column to highlight the current week when users land on a specific week page.

Standard obstetric convention counts gestational weeks from the last menstrual period rather than from conception, which means weeks 1 and 2 occur before fertilization in most pregnancies. The widget should use the LMP convention by default and offer a conception-date toggle for users who want to think in fertilization-age terms. The intro and FAQ columns should call out the convention explicitly so users see which model the page uses.

Treat the screening, milestone, and red-flag columns as living data. When ACOG publishes a guideline update, like a revision to the glucose tolerance test timing or a new genetic-screening recommendation, edit the relevant week rows and flush. Every affected week page picks up the new guidance. Medical reviewers can audit the full forty-two-week corpus by scanning the sheet on a single screen.

Yes. Add a multiples-specific page group with its own urlPattern like /pregnancy/twins/week-{n}/ pointing at a separate sheet with twin-pregnancy-specific milestones and screenings. The base widget can detect the multiples flag and adjust the displayed due-date convention because multiples often deliver earlier than the standard forty-week due date. Two page groups, two coherent variant trees, one shared widget pattern.

Add a column for conception_method and have the widget adjust the LMP-versus-transfer-date defaults. IVF pregnancies typically count from the embryo-transfer date plus a known embryo age rather than from a back-calculated LMP. The intro and FAQ columns can clarify the convention for these users. A separate page group with /pregnancy/ivf-week-{n}/ might earn its place if the editorial scope justifies the additional URLs.

Use a trimester column that the widget can highlight on the navigation bar. Trimester boundaries vary by convention. Many sources mark first trimester as weeks 1-12, second as 13-27, third as 28-40. Some sources extend the first trimester through week 13 because that aligns with the screening windows. Pick one convention and document it in the intro across every week page in the group.

Yes. The base widget is exactly that. Users land on /pregnancy/week-12/ for the milestone content and can enter their LMP or due date in the widget to see where they actually are in their own timeline. The widget then optionally links to the user's actual current week page if it differs from the page they landed on, which improves navigation and time-on-site metrics.

The standard week catalog covers weeks 1-42 because deliveries beyond 42 weeks are post-term and clinically uncommon. The week-42 page should call out the post-term threshold and the typical induction-of-labor recommendations rather than implying a normal continuation into week 43. The widget should still compute weeks accurately for users at 42+1 days or later but the dedicated landing pages stop at week 42.