One name and one known relationship are enough[cite: 3]. Add close relatives first and leave uncertain dates or places blank until stronger information is available[cite: 3].

Starting with yourself is usually easiest for general genealogy[cite: 3]. A reunion or descendant tree may begin with a shared ancestor or couple[cite: 3].

Guest editing may be available, but an account is recommended for secure online backup, access from different devices and private collaboration[cite: 3]. Check the current product flow before publishing this answer[cite: 3].

You can start without entering payment information[cite: 3]. The Pricing page should show verified limits for trees, people, storage, collaborators and exports[cite: 3].

Yes[cite: 3]. Choose a three-generation, ancestor, descendant, photo, blended-family, school or reunion template and customize it in the editor[cite: 3].

Open the profile of a connected person, choose the relative you want to add, select the relationship type and review the new connection[cite: 3].

Yes, when the corresponding relationship choices are enabled[cite: 3]. Use accurate labels and review how the connection appears in shared and printed views[cite: 3].

Yes[cite: 3]. Add each partner as a separate relationship and connect children to the correct parents[cite: 3]. Check the chart after adding remarriages[cite: 3].

Edit or remove the relationship from the affected profile[cite: 3]. Do not delete the entire person unless the profile itself is unwanted[cite: 3].

Compare dates, places, parents, partners, children, occupations and sources before merging[cite: 3]. The same name alone is not enough[cite: 3].

Leave it blank or record an approximate value such as about 1885[cite: 3]. Do not invent a precise date to make the profile look complete[cite: 3].

Yes[cite: 3]. Add a clear profile image and record who supplied it, when it may have been taken and who appears in it[cite: 3].

Avoid identification, financial, medical and other sensitive documents[cite: 3]. Collect only what the project genuinely needs[cite: 3].

Civil certificates, census records, church registers, obituaries, military files, books, letters, photographs and recorded interviews can all support family information[cite: 3].

Keep both versions in a note, compare the evidence and mark the fact as conflicting until a stronger conclusion can be made[cite: 3].

GEDCOM is a text-based format used to exchange structured genealogy data between compatible programs[cite: 3]. Files commonly end in .ged[cite: 3].

If the service provides a GEDCOM export, upload it into a new private tree and review the result before deleting the original[cite: 3].

Usually not as complete image files[cite: 3]. Photographs and documents often need to be transferred separately[cite: 3].

No[cite: 3]. GEDCOM transfers structured data rather than the original visual layout[cite: 3]. Custom fields and relationship styles may also differ[cite: 3].

The source may already contain duplicate profiles, or the same data may have been imported more than once[cite: 3]. Compare evidence before merging[cite: 3].

It provides a portable data backup for migration and recovery[cite: 3]. Keep a separate media folder and a readable PDF as well[cite: 3].

A new tree should be private by default[cite: 3]. It becomes visible to other people only when the owner invites them or deliberately publishes a limited view[cite: 3].

Shared views should hide exact dates, contact details, private notes and sensitive documents[cite: 3]. Verify the precise behavior in the product’s Privacy and Security page[cite: 3].

Invite trusted people individually and assign viewer or editor access[cite: 3]. Create a backup before major collaborative changes[cite: 3].

Yes[cite: 3]. Remove the person’s access in the tree settings[cite: 3]. Information already copied or downloaded cannot be recalled[cite: 3].

Private trees should not be crawlable or indexed[cite: 3]. Public pages about living people should remain protected according to the verified privacy design[cite: 3].

Use the verified deletion route in account settings and review retention timing[cite: 3]. Export GEDCOM and media before deleting anything you may need[cite: 3].

PDF is usually best for home or professional printing[cite: 3]. SVG is useful for large posters when the printer supports it[cite: 3].

Too many people or fields are being compressed into the selected page[cite: 3]. Use larger paper, simplify profiles or split the tree into branches[cite: 3].

Sometimes, but the result may not be readable[cite: 3]. A poster or several branch charts often works better[cite: 3].

Yes[cite: 3]. Choose a blank template, hide unused fields and export a PDF with enough space for handwriting[cite: 3].

Avoid exact birth dates on reunion, school or public displays[cite: 3]. Use a year or hide the field[cite: 3].

The Pricing page must list verified tree, person, storage, collaborator and export limits[cite: 3]. Do not rely on a generic ‘free’ claim[cite: 3].

Review the verified rules for viewing, editing, exporting, excess storage and deletion[cite: 3]. Create backups before cancellation[cite: 3].

Use the password-reset link on the verified sign-in page[cite: 3]. Support should never ask you to send your existing password[cite: 3].

No standard support process should begin with an unexpected request for payment, passwords or remote computer access[cite: 3]. Use only verified website channels[cite: 3].

Provide the page, expected behavior, actual result, exact error, browser, device and a redacted screenshot[cite: 3]. Do not post private family files publicly[cite: 3].