Daykin Family Law

The structured data present is limited to WebPage, BreadcrumbList, and WebSite schema — all auto-generated by Yoast or a similar plugin. There is no LegalService, LocalBusiness, Attorney, or LawFirm schema type, which means AI systems cannot confidently identify this as a law firm, its practice areas, its geographic service area, or its key personnel. The WebSite schema has an empty 'description' field ('@id': '#website', 'description': ''). No FAQPage, ContactPoint, or OpeningHoursSpecification schema is present on the contact page. The footer copy does describe the firm's services in plain text ('full-service family law firm offering tailored solutions in all areas of separation, divorce, property settlement...') which is citable, but it is not structured in a way that AI systems can reliably extract and attribute.

The page copy is minimal: one short paragraph explaining meeting options (office, Noosa, phone, video) and then raw contact details. There is no copy that addresses the emotional state of a prospective client — no mention of confidentiality, no indication of what happens after they submit the form, no response time commitment, and no reassurance about cost of the initial consultation. The CTA 'Book an Appointment' appears three times in the header alone, which is repetitive rather than persuasive. The form's 'Type of Enquiry' dropdown includes 'Starting relationship', 'Ending Relationship', and 'Binding Financial Agreement', which is useful segmentation, but the form itself has no supporting copy to guide the user.

The logo appears to be rendered twice in the header (SVG and PNG versions) and again in the footer, suggesting a dual-logo setup that may cause visual redundancy. Award badge images ('Parenting Leading 2026', 'Family Recommended 2026') appear in the footer but one badge image filename is duplicated ('Family-Recommended-2026.png' appears twice), suggesting a copy-paste error in the template. The heading hierarchy is shallow — H1 'Contact', then the form fields — with no H2 or H3 subheadings to break up the page or signal content structure to crawlers. Alt text on the award badges is present as filenames only, not descriptive text.

The H1 is simply 'Contact' — functional but completely devoid of reassurance for someone in a stressful family law situation. The sub-headline 'Convenient locations in Fortitude Valley (close to Brisbane CBD) & Noosa' is the first piece of genuinely useful information and it does the heavy lifting. The page title in the browser tab repeats a long GUID string ('AEB11319-1864-4BD0-B94B-6399CACDFE02') three times, which is a technical rendering artefact that looks broken and unprofessional to any visitor who notices it. The sticky footer with two scenario-based CTAs ('I'm Thinking of Separating' and 'I'm in Court') is a smart UX touch that survives onto this page.

Two award badges ('Parenting Leading 2026', 'Family Recommended 2026') appear in the footer, which is positive, but they are small, positioned below the fold, and lack any explanatory text about what organisation awarded them. Social media links to Instagram, Facebook, and LinkedIn are present. The footer includes the legally required disclaimer 'Liability limited by a scheme approved under professional standards legislation.' There are no client testimonials, no lawyer names or photos, no bar admission details, and no Google review count visible on this page. The contact page is the highest-intent page on the site and it has the least trust content.

The meta title 'Contact | Daykin Family Law' and meta description 'Get in touch with Daykin Family Law for expert family legal advice. Call, email, or book a confidential consultation with our Brisbane team.' are both present and well-formed. The description is concise and includes a location signal ('Brisbane'). The site ranks #1 organically for its own brand name, which is expected. The contact page itself is unlikely to rank for any non-branded queries given its thin content. The GUID string appearing in the scraped page title ('AEB11319-1864-4BD0-B94B-6399CACDFE02' repeated three times) may be a rendering issue but warrants investigation as it could appear in cached versions. Breadcrumb schema is present and correctly structured.

The contact form is well-structured with required fields for first name, last name, email, phone, preferred location, and type of enquiry — the location and enquiry-type dropdowns are particularly good for routing leads internally. The phone number is prominently displayed and linked as a tel: URI. However, there is no indication of response time, no privacy reassurance adjacent to the form, and no confirmation of what a 'consultation' involves or costs. The CAPTCHA is present which is good for spam prevention. The sticky footer scenario CTAs ('I'm Thinking of Separating', 'I'm in Court') are conversion-positive but link away from the contact page rather than anchoring to the form.